Tracking traffic sources across domain redirect - dns

I have a domain AAAA.com which is used for marketing an App. It redirects to a page on another domain: BBBB.com/buy-app.php, where Google Analytics is set up.
How do I on BBBB.com/buy-app.php track where the traffic is coming from?
E.g:
An users clicks on a link to AAAA.com on Facebook, which redirects to BBBB.com/buy-app.php – how do I the know where the user came from?

You're talking about "Tracking Multiple Domains": Google Analytics for Developers: Tracking Multiple Domains
For this same use case, I prefer to use Google Analytics on Steroids: Google Analytics on Steroids: Cross Domain Tracking
_gas.push(['_setAccount', 'UA-XXXXX-1']);
_gas.push(['_setAllowLinker', true]);
_gas.push(['_setDomainName', 'AAAA.com']);
_gas.push(['_setDomainName', 'BBBB.com']);
_gas.push(['_gasMultiDomain', 'mousedown']);
* Note: calling _setDomainName multiple times is only supported in _gas and not supported by the default _gaq.

Related

How to make my website not dangerous when doing a phishing awareness campaigns?

So I have a website that send phishing emails for employers and I get the results for this campaign (for example how many employees click on the link, etc)
While testing my website on my personal emails the website became dangerous.
What should I do ?
Disclaimer - I run a phishing simulation service called CanIPhish and I came across this exact same issue when building my phishing websites.
What's happening here, is google is discovering and analysing your website through both it's normal indexing capability but also by scanning emails and detonating links.
When Google or it's threat intelligence partners discover your website it's analysing the content and accordingly flagging it as malicious.
To get around this issue, you need to hide the website behind a load-balancer or CDN which can perform conditional routing based on querystring parameters. Within the querystring you need to create a single-use GUID tied to the campaign and target. When the target detonates the link, they're forwarded to the phishing website and the GUID becomes inoperable. This way, when google or a threat intelligence partner index the site or detonate links in an email, they see something completely different to what your actual targets see.
I'm operating my myriad of phishing websites by hosting them on Amazon S3, I'm using Cloudfront as the CDN, Lambda#Edge on Cloudfront to inspect QueryString parameters and a mixture of DynamoDB with S3 for storing target user details and details on whether a GUID has already been detonated.
To see an example of this - try browsing here and all you'll see is a "Oops you clicked a phishing link" instead of the actual page which is a Google phishing site.

Adobe Analytics cross-domain with Experience Cloud ID

I ask your help to better understand if my cross-domain tracking (Adobe Analytics via Experience Cloud ID) is working properly. To me it seems not.
As you see in screenshot 1, my visits might come from Domain A and go, within the same session, to Domain B. We're collecting data, from both domains, to the same AA Report Suite.
The Experience Cloud ID Service is active, in the same way, to both configurations (same mc org id, as you see).
Into Analytics Workspace (screenshot 2) I created a fallout analysis to show how visits move from Domain A to B. The Analysis is based on two segments including visits that in turn include hits for domain A or B.
I expected to see Domain A visits to be distributed also to the Domain B, but it seems not. No visits are going there...how could it be?
Am I missing something with the Experience Cloud ID configuration ?
Thanks so much
The out of box setup for Adobe Experience Cloud Visitor ID Service requires the browser to be able to access a third party call to a subdomain under demdex.net, and then stores a cookie containing the user's identifier under demdex.net domain. See Adobe's KB for more detailed description of the process.
If the browser for whatsoever reasons cannot save or read the cookie, then as the visitor goes from site A to site B, the JavaScript JS library (i.e. Visitor.js) will keep requesting on a set of identifiers from demdex.net or failing contacting demdex.net generate a set of identifiers locally.

Tracking traffic from a third party app

I work for a company which is essentially a jobs board. We have partnered with an organization and they have agreed to post our job feed on their app. How do I track the traffic coming from this app to my website? Please advise. The jobs are posted as an iframe. Do I need to use UTM tags to identify the traffic? If yes, the URLs are dynamic as of now so how do I implement the tags?
Per job you generate an URL link.
With your RSS-feed you implement an URL... in that URL you should have the UTM tag included and analytics installed on your website.
See here where that is explained in great detail. Also, check the tutorials from G analytics itself in detail.
For example, on website A there is a link to website B: http://www.websiteb.com/. Provided that website B has Google Analytics installed, visits from website A will show up in Google Analytics as
Source = http://www.websitea.com
Medium = referral
... the essentials explain here:
The tracking standard used by Google Analytics is called UTM parameters. Because Google Analytics is the de facto standard for website analytics, the same applies to UTM parameters. You have probably noticed these at some point in the browser URL field after clicking a link. A typical URL in an ad could look something like this:
http://www.website.com/?utm_source=newssite.com&utm_medium=cpc&utm_campaign=my-campaign
Everything after the “?” in the URL above is information for Google Analytics to correctly categorize visits from this link to the website.

will google analytics work with multiple sharepoint zones?

I have a SharePoint 2010 site that has both Internet and Intranet zones. I want to capture internal and external traffic to the site.
Internet access uses forms based authentication and Intranet access uses windows authentication.
Internet: http://www.thesite.org
Intranet: http://thesite
Apart from the landing pages, both sites are the same. Google Analytics Support suggests that the Intranet must be accessible by a fqdn. But I guess that doesn't apply in this case.
So if I place a google analytics tracking code in my master page would it capture the traffic from both sources? Or do I need a different approach?
This will probably not work by default - IIRC cookies can only be set on a fully qualified domain name, and since GA uses cookies it will not work on http://thesite.
A possible workaround might be to disable cookies in GA by setting storage:none when you create the tracker; in that case you have to supply and maintain your own clientid, e.g.
ga('create', 'UA-XXXXX-Y', {
'storage': 'none',
'clientId': '76c24efd-ec42-492a-92df-c62cfd4540a3'
});

Google Analytics Handling multiple domains

Hello There I have 3 different sites hosted on same server having different domains. Let's say they are
www.abc.com
www.xyz.com
www.mno.com
I have successfully integrated google tracking code (using ga.js) and get data through reporting api for www.abc.com. Now I also want tracking of data and getting data for others too. What I need to do that? Can I create seperate profiles in same google account for all three sites? Or I need to create separate google analytics account for each site or I can do it with same profile and same account?
I have searched but couldn't be able to find out any solutions. Please guide.
GA is structured in an Account --> Property --> Profile way.
So for your example I would suggest the best method would be to run all the sites in the same account, but create a new Property for each site.
When you do this GA will give you a new UA-xxxxxx-x number for each site.
Check this out for more help https://support.google.com/analytics/answer/1042508?hl=en-GB&ref_topic=1009620
Cheers
John

Resources