Tutorial // Cross-Domain Tracking with Google Tag Manager

Tutorial // Cross-Domain Tracking with Google Tag Manager

Does your website span multiple domains? Learn how to quickly configure cross-domain tracking for Google Analytics using Google Tag Manager. You’ll learn how to adjust your tag so that each user is reported once (instead of twice) inside your reports.



Tracking events with Google Tag Manager: https://www.youtube.com/watch?v=zrI0FlNSSA0 />Tracking embedded YouTube videos with Google Tag Manager: https://www.youtube.com/watch?v=XGxbhu9-FWc />Tracking site search without query parameters using Google Tag Manager: https://www.youtube.com/watch?v=D_vLHRB4kOw />My Google Tag Manager course: https://www.lovesdata.com/courses/google-tag-manager


SUBSCRIBE FOR MORE VIDEOS: http://www.youtube.com/subscription_center?add_user=lovesdata />

Twitter: https://twitter.com/lovesdata
Facebook: https://www.facebook.com/LovesData/
LinkedIn: https://www.linkedin.com/company/loves-data
Google+: https://plus.google.com/+LovesData

Welcome to my YouTube channel! I’ll be teaching you how to get the most out of your data to improve your website and online marketing, with a focus on Google AdWords and Google Analytics. Thanks for your support!

10 thoughts on “Tutorial // Cross-Domain Tracking with Google Tag Manager”

  1. Thanks, this is a great tutorial! In GTM it's possible to setup cross domain tracking via a Variable, or via a Tag. Questions: 1. Can you give examples of best case scenarios for each? 2. What would the outcome be if cross domain tracking is setup (exactly the same) in both the Variable and the Tag?

  2. Thanks for the well articulated video! So clear and your voice is so crisp!

    What about sub-domain tracking? Does we follow the same steps as the video for sub-domain tracking for UA?


  3. I have been creating separate account for each domain until now. I do not understand how to use 2 domains with the same tracking code. Will that not mix all the data together? Audience overview etc? I want to cross-domain track sessions but still be able to check each domain data separately :S. How is that possible?

  4. This is helpful and clear to understand and implement ….however it seems there is much more to cross domain tracking that we still need to make sense of (future video idea?? 🙂 For example: Does the cross domain tracking only count the next page or does the session persist all over the second domain? Will the content of the second domain appear in the analytics of the first domain? what are the implications to goals? what are the limitations of cross domain tracking? When the second domain has its own analytics account is there any risks or limitations to having multiple analytics IDs? Thanks!

  5. Great video! I don't see any reference to adding the impacted domains to the Referral Exclusion List, which I usually see considered a requirement for setting up cross-domain tracking. Was that an oversight to not include it or was that purposeful as you don't deem that updating the Referral Exclusion List is necessary?

Leave a Comment

Your email address will not be published.