{"id":4065,"date":"2020-05-12T09:48:52","date_gmt":"2020-05-12T09:48:52","guid":{"rendered":"https:\/\/chef-dev.creativegeek.co.il\/?p=4065"},"modified":"2022-11-08T11:06:31","modified_gmt":"2022-11-08T08:06:31","slug":"the-curious-case-of-google-analytics-cross-domain-tracking","status":"publish","type":"post","link":"https:\/\/trackingchef.com\/google-analytics\/the-curious-case-of-google-analytics-cross-domain-tracking\/","title":{"rendered":"The Curious case of Google Analytics Cross-Domain Tracking"},"content":{"rendered":"\n
A recent call from a past client reminded me of an interesting use case worth sharing.<\/p>\n\n\n\n
I had just left the ad agency I was working at and switched over to the relaxed client-side life as an in-house Digital Marketing manager.<\/p>\n\n\n\n
One day while I\u2019m at the office, I received a phone call from an unknown number.<\/p>\n\n\n\n
\n\u201cI\u2019ve got your number from a mutual friend\u201d<\/p>\n<\/blockquote>\n\n\n\n
said the man on the other side of the line<\/p>\n\n\n\n
\n\u201cWe have a tracking issue we can\u2019t solve. I can\u2019t tell where my conversions are coming from!\u201d<\/p>\n<\/blockquote>\n\n\n\n
The client was a luxury hotel chain managing several web properties. Each of their two brands had a dedicated website, split across two domains, one for each language (Hebrew & English). So overall they had four internal domains to manage:<\/p>\n\n\n\n
\n
- hotel-a.com<\/li>\n\n\n\n
- hotel-a.co.il<\/li>\n\n\n\n
- hotel-b.com<\/li>\n\n\n\n
- hotel-b.co.il<\/li>\n<\/ol>\n\n\n\n
Aside from the multiple client domains, the reservations were handled on a third-party site, so the conversions were ultimately happening there. For sake of simplicity, let\u2019s call it reservation-site.com<\/p>\n\n\n\n
Classic cross-domain setup.<\/p>\n\n\n\n
\n\u201cLet\u2019s rock and roll\u201d<\/p>\n<\/blockquote>\n\n\n\n