AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

Analytics
1.8K members online now
1.8K members online now
Dive into multiple domain (Cross/Sub) tracking, implementing Ecommerce and Enhanced Ecommerce, setting up Event tracking, and Universal Analytics code.
 
Guide Me
star_border
Reply

Inaccurate Cross-domain tracking

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi all, 

 

We've implemented cross-domain tracking between 2 websites we have by using the same property and view for those 2 sites.

It works like a charm.

Nonetheless, we kept our current stand alone tracker on the 2 sites.

So that means that we have current setup own each domain:

- one standalone tracker for the site trafic

- one cross-domain tracker to monitor the handover between the 2 sites.

 

We've also added an exclusion list for both domain.

 

The issue we currently face is that page views from the cross-domain tracker are different than from the standalone tracker for a given page. 

The difference can be as high as 20%.

 

Any idea where to look to correct this issue or to understand it ?

This is really confusing as it should definitely match, both trackers monitor the same thing on a page.

 

Any help in a direction would be great as we're kind of out of idea at the moment.

 

Kind regards

David

 

Re: Inaccurate Cross-domain tracking

Explorer ✭ ✭ ☆
# 2
Explorer ✭ ✭ ☆
Hi David,

So in total you have 2 snippets, both on each site?

1 snippet that's measuring just that site, another that counts that site plus your other site?

Did you set this up with a subdomain or an entirely different website?

Ali

Re: Inaccurate Cross-domain tracking

[ Edited ]
Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

Hi Ali

Here is what we have for each site, both on 2 different domains.
YYYYY is the ID on the same property we're using for cross domain tracking.

(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','__gaTracker');

__gaTracker('create', 'XXXXXX', 'auto');
__gaTracker('set', 'forceSSL', true);

__gaTracker('create', 'YYYYYY', 'auto', {'name': 't2', 'allowLinker': true});
__gaTracker('t2.require', 'linker');
__gaTracker('t2.linker:autoLink', ['other domain']);
__gaTracker('t2.send', 'pageview');

__gaTracker('require', 'displayfeatures');
__gaTracker('send','pageview');

Any idea ?

Re: Inaccurate Cross-domain tracking

Explorer ✭ ✭ ☆
# 4
Explorer ✭ ✭ ☆
Hi Sean,

You mentioned another tracker on a different view/property where you were comparing pageviews - can you share that as well?

The URLs of the sites would help too but I understand if you don't want to share those - but they really would be helpful

Ali

Re: Inaccurate Cross-domain tracking

Visitor ✭ ✭ ✭
# 5
Visitor ✭ ✭ ✭
On the other property, it the same basically
__gaTracker('create', 'ZZZZZZ', 'auto');
__gaTracker('set', 'forceSSL', true);

__gaTracker('create', 'YYYYYY', 'auto', {'name': 't2', 'allowLinker': true});
__gaTracker('t2.require', 'linker');
__gaTracker('t2.linker:autoLink', ['first domain']);
__gaTracker('t2.send', 'pageview');

__gaTracker('require', 'displayfeatures');
__gaTracker('send','pageview');

main site is beesapps d o t com and conversion site is beesy d o t me on the subscribe page