Google Analytics Cross-Domain Conversion Tracking and Attribution to AdWords Campaign - google-analytics

Background
We have a number of websites that we maintain and we have Google AdWords Campaigns running to drive traffic to these sites.
For Example:
www.example1.co.uk
www.example2.co.uk
www.example3.co.uk
After browsing these sites, a customer will be redirected to our E-Commerce platform if they decide to make a purchase (this is where the conversion happens):
www.example-checkout.com
Current Google Analytics Setup
Our current Google Analytics Setup looks like this:
www.example1.co.uk, www.example2.co.uk, www.example3.co.uk
ga('create', 'UA-12345678-1', 'auto', {'name': 'globalTracker'});
ga('globalTracker.send', 'pageview');
ga('globalTracker.require', 'linker');
ga('globalTracker.linker:autoLink', ['example-checkout.com'], true);
www.example-checkout.com
All Pages
ga('create', 'UA-12345678-1', 'auto', {'allowLinker': true, 'name' : 'globalTracker'});
ga('globalTracker.send', 'pageview');
Checkout Page Only
The checkout/confirmation/thank you page contains additional calls to load the Google Analytics E-Commerce plugin and post the details of the transaction that has occurred.
ga('create', 'UA-12345678-1', 'auto', {'allowLinker': true, 'name' : 'globalTracker'});
ga('globalTracker.send', 'pageview');
ga('globalTracker.require', 'ecommerce', 'ecommerce.js');
ga('globalTracker.ecommerce:addTransaction', {
'id': '${transactionID}',
'affiliation': '${affiliation}',
'revenue': '${revenue}',
'shipping': '${shipping}',
'tax': '${tax}'
});
ga('globalTracker.ecommerce:send');
What Works
The E-Commerce tracking code appears to work and conversions are recorded. In Google Analytics we can see that we received traffic/clicks from our AdWords campaigns which suggests that the _ga cookie is being correctly passed cross-domain from www.example1.co.uk to www.example-checkout.com (in fact I have verified this using the Chrome Developer Tools / Google Analytics Debugger Plugin).
Problem
The problem is that the conversions are never attributed to the AdWords Campaign & AdGroup. The source of the conversion is always a referral (E.g. from www.example1.co.uk).
What am I missing? I want to see the conversions attributed to the AdWords campaign. I.e. in the "Acquisition -> Campaigns" section of Google Analytics.
Any pointers are greatly appreciated.

You do not mention that you use any decorator functions (i.e. functions that add the ga parameter to outgoing links, forms etc.) and allowLinker does not do this automatically. So it should be not possible that cross domain tracking works at all (i.e. both domains will be tracked but on changing the domain the user will start a new tracking session). (UPDATE: Sorry, I did not see the autolinker plugin in the code, so ignore this paragraph).
Plus you need to add both domains to the referrer exclusion list in the property settings (this will remove the referrer no matter what, so make sure that the client id is passed on before you do that).
Unless you have used decorators without saying so in the question this is most likely your problem. Look into the outgoing urls if the ga parameter is appended when switching domains and make sure that the ga code on the other domain does actually receive the parameter (i.e. if there are redirects make sure they retain the parameter).

Related

Cross Domain Tracking script into Google Tag Manager settings?

I am trying to set up my website to have cross domain tracking with the online store Gumroad.com, inside my Google Analytics. So that I can follow the user events from one site onto the next.
Gumroad has instructions at this link, but they are in the format of a script to be pasted into the site.
I use Tag Manager and am wanting to input these parameters into my Google Analytics Settings variable (which is how Google recommends doing Cross domain tracking with Tag Manager)
I'll attach the script that they provided, as well as my Google Analytics Settings variable in Tag Manager. If anyone knows how to set up the rest of the parameters that would be greatly appreciated!
Script:
<script>
// mystorefront.com is your site's domain.
ga('create', 'UA-XXXXX-Y', 'mystorefront.com;, {'name': 'sampleTracker', 'allowLinker': true, ';cookieDomain': 'mystorefront.com'});
ga('sampleTracker.require', 'linker');
ga('sampleTracker.linker:autoLink', ['mystorefront.com']);
ga('sampleTracker.send', 'pageview');
</script>
My Tag Manager (Google Analytics Settings variable) setup so far:
[]
Set domains in list without protocol.
It also does not make sense that you use cookieDomain as Field to set when it is already defined in the field below the tracking ID.

Custom Campaign tracking Cross-Domain Google Analytics

I have successfully implemented Cross-Domain tracking with Google Analytics (1 session as user jumps across domain, same _ga cookie on both domains, etc.) However, when the user jumps to the second domain and completes a purchase, the eCommerce transaction is not getting attributed to the utm custom campaign from the first page. It seems you can't pass the utm custom campaign information cross-domain. Is this true? Has anyone ran into this before?
I found my issue, cache. I have done hard refreshes before every test, but I went into Chrome tools and clear EVERYTHING. Cookie, cache, everything. And Cross-Domain tracking for Custom Campaigns started working! For reference here are the scripts for the two sites:
Site 1:
ga('create','UA-xxxxxxx-x'','auto', { 'allowLinker': true });
ga('require', 'linker');
ga('linker:autoLink', ['site2.com']);
ga('require','ecommerce','ecommerce.js');
ga('send','pageview');
Site2:
ga('create', 'UA-xxxxxxx-x', 'auto', { 'name': 'client', 'allowLinker': true });
ga('client.require', 'linker');
ga('client.linker:autoLink', ['site1.com']);
ga('client.require', 'ecommerce', 'ecommerce.js');
ga('client.send', 'pageview');
Also, I added site1.com and site2.com to the Referral Exclusion List in GA and the UA key for site 1 and site 2 are the same.

cross domain tracking goals go to direct

I have an issue with cross domain tracking for one of my clients.
When people go from one site to the the other they go to a different domain. There they finnish a servey and they convert on that site.
I have analytics set up and the data comes in from both websites, but the conversions are registered for direct en referral. I want to know what keywords in Adwords turned into the conversion.
can someone help me with this issue?
You'll need to set up cross domain tracking as described in this support article.
If you use Google Tag Manager, you can use the "Auto Link Domains" functionality that will take care of the details.
Otherwise, you'll essentially have to change the intialization of your tracking snippet from
ga('create', 'UA-XXXXX-Y', 'auto');
to
ga('create', 'UA-XXXXXXX-Y', 'auto', {'allowLinker': true});
ga('require', 'linker');
ga('linker:autoLink', ['your-second-domain.com'] );
Note that these solutions always require that you use the same Analytics property ID on both sites.

How to I correctly attribute channels from the Google Analytics Measurement Protocol?

We are trying to attribute user actions that happen after a user has signed in to the marketing channel they originated from. To do this, we use the standard Google Analytics JS library as well as the Measurement Protocol. Events get tracked in Google Analytics and they are visible in the events view. However, they do not get attributed to the correct campaign and only show up under the Direct channel.
Our process is as follows:
The user gets tracked with front end Google Analytics JS on our site:
ga('create', ‘UA-XXXXX-Y’, 'auto');
ga('send', 'pageview');
A userId gets assigned to the user in Google Analytics as soon as they sign up:
ga('create', ‘UA-XXXXX-Y’, 'auto');
ga('set', 'userId', 'fe8220b3');
ga('send', 'pageview');
Once a certain action we would like to track happens, we send a GET request to the Measurement Protocol with the following params:
v: 1,
t: 'event',
tid: ‘UA-XXXXX-Y’,
cid: ‘555’,
uid: ‘fe8220b3’,
ec: ‘backend_action’,
ea: ‘action’
This correctly tracks the event, but does not associate it with the user. As far as I understand, since we have provided the same UserId in our params that we did when identifying the user, the attribution should happen automatically in Google Analytics. Am I misunderstanding how this works?

Can I track Adwords banner click from the other website?

I have an Adwords campaign, it sends users to Website-1.
And there is Website-2 and I want to track whether users that came to Website-2 have ever clicked on Adwords banner leading to Website-1 or not.
I could have set third-party cookies on Website-1 corresponding user is from Adwords and then get this info on Website-2. The problem is I don't have access to Website-1.
Is there any way to gain this info? I do have access to Adwords campaign, it's Google Account, Google Analytics on Website-2, it's Google Account and Website-2 itself. In other words, I have access to everything except Website-1
You might use third-party redirect/counter, for example different ad-serving tool like AdForm, where you should be able to generate unique redirect URL in bulk for your campaign.
Disadvantages:
you loose gclid information on AdWords tracking (because of redirect) and you need to use manual UTM tagging
You need to pay ad-serving fee (few bucks for thousands of visitors) and someone to set it up
You would only know if that someone clicked AdWords Ad, not really visited (beacuse you would count before that someone landed)
In conclusion: don't do it if you don't have direct access to GA of website-1
Yes you can do this in a pretty simple way, just set up Cross Domain tracking as described here:
https://support.google.com/analytics/answer/1034342?hl=en
This will save original source information (including AdWords) wen user goes from Website-1 to Website-2. On Website-1 you need to edit Analytics code (on all pages) and add so called autoLink:
ga('create', 'UA-XXXXXXX-Y', 'auto', {'allowLinker': true});
ga('require', 'linker');
ga('linker:autoLink', ['example-2.com'] );
Make sure that on both websites youre using newest version of Google Analytics: Universal Analytics, because this will not work in older version

Resources