3. Understanding Cross Domain Tracking
A Visitor comes originally from traffic source eDM to your website www.abc.com. Same visitor
navigates towards checkout on your website, but your checkout system is on a different
domain abccart.com.
Without cross tracking original visitor session will be lost when your visitor crosses over to your
checkout domain, therefore your visitor is split into 2; Visitor A and Visitor B even though it’s
the same visitor. Most importantly, the original traffic source eDM is lost, now traffic source for
visitor B will be abc.com (self referral)
4. Understanding Cross Domain Tracking
The analytics.js library uses a single first-party cookie to store the Client ID
that can only be accessed by the domain on which it is set. If your visitors
traverse from your domain to a third-party domain (e.g. payment gateway) this
cookie is lost therefore original session is lost. Cross domain tracking ensures
that the analytics.js cookie data is maintained across each of these domains
traversed.
7. Understanding Cross Domain Tracking
Loads the linker plugin
Define which domains to
auto link e.g. shopping cart
domain
Setting Up Cross Domain Tracking
autoLink Plugin
8. Understanding Cross Domain Tracking
Setting Up Cross Domain Tracking
autoLink Plugin
If you have implemented the autoLink plugin correctly,
whenever you click on links that lead to the 3rd party (e.g.
shopping cart) domain, you should see the URL is attached
with the _ga query string as follows:
9. Understanding Cross Domain Tracking
Setting Up Cross Domain Tracking
autoLink Plugin
Now on the third party domain, update the create function to
enable linking by setting the allowLinker attribute to true
ga('create', 'UA-XXXXXX-X', {
'allowLinker': true
});
