Like the October 8, 2011 announcement that Google would begin to stop the practice of passing a user’s organic search term to Google Analytics; the deprecation of the Service Provider dimension on February 4th, 2020 may live on with similar disdain. While we mourned the loss of the search keywords data that helped value our SEO efforts; at least there was a reason – better security and privacy.
In Google Analytics, dimensions are characteristics of the user that visited your site and include things like: browser & version, operating system, campaign, channel, screen resolution, and many, many more. (Visit the Google reference on dimensions for a complete list.) While Google Analytics has over 125 (more if you use AdWords and / or Ecommerce) dimensions already baked-in and set for you; users of the free platform can add their own – up to 20.
Earlier this year, we posted a walkthrough to help you deploy Google Analytics Cross Domain Tracking via Google Tag Manager. (To learn more about this topic, check out our quick video which covers all the benefits of cross domain tracking in Google Analytics).
This post will cover the same topic, but instead of using Google Tag Manager, we will customize the base Google Analytics Tracking Code (GATC).
As we did in out last post, let’s begin with the sample use case:
Your site links to another top level domain where some sort of conversion (sale, registration, etc.) takes place.
e.g. A visitor lands on example.com and registers on conversion.com
In this scenario and using the default version of the GATC, your conversions will all show as referrals from example.com and the original channel data (organic, email, paid, etc.) will be lost. That makes it very hard to determine which channels, sources, keywords and campaigns are effective!Read More