API Connector Add-On for Google Sheets
Check out my API Connector Add-on to easily connect and pull data from thousands of platforms (e.g. Shopify, Harvest, Mailchimp, ActiveCampaign, Google Ads, YouTube, etc.) directly into Google Sheets.
Working as a Google Analytics / Google Tag Manager consultant, it’s common to navigate around the web with tools like the Google Analytics Debugger and Google Analytics Tag Assistant still active in the browser. These tools display information about every tracking call sent to Google Analytics’ servers, allowing you to view and debug the GA implementation of any website. I noticed Google Analytics uses Google Analytics on its own site to track itself. This is a bit meta, but I thought it might be worth looking at more deeply — they created the tool; maybe they’re using it in some interesting or non-obvious ways.
GOOGLE ANALYTICS SELF TRACKER REVIEW
GA is sending user information to at least 4 different trackers. The debugging tool showed that there was an attempt to send data to a 5th tracker (UA-38676921-24), but it got blocked with the error message ‘Aborting cookie write: Prohibited domain.’.
The top account, UA-10005-1, is using the old legacy (‘classic’) GA code, while the bottom 3 are using the newer Universal Analytics syntax. Google Tag Manager is also active on the Google Analytics site, but isn’t firing GA code.
VIRTUAL PAGEVIEWS (URL RE-NAMING)
The 3 Universal Analytics pageview tags all sent a variation of the actual URL path to GA.
Original URL path: /analytics/web/#home/a8399080w96273388p100425068/
Revised URL path: ga(“set”, “page”, “/analytics/web/home/”)
This does 2 things: strips out the hash tag from the URL and removes the unique string at the end of the URL. That makes sense to allow them to aggregate all their user data together.
This convention of simplifying URLs was followed on other pages; for example, /analytics/web/#embed/report-home/a8399080w96273388p100425068/ became /analytics/web/embed/report-home
CUSTOM DIMENSIONS AND VARIABLES
Below are the details of custom dimensions /variables set by the four active GA trackers. Custom variables were the precursor to custom dimensions, and are only used by the legacy GA code (UA-10005-1). Custom variables also have names attached, while the dimensions use numbers instead, adding some opaqueness to what is actually being tracked.
|UA-10005-1 (classic) +|
|UA-38676921-2 (Universal) +|
|CONTENT GROUP 2||ungrouped|
|UA-38676921-4 (Universal) +|
|CONTENT GROUP 2||ungrouped|
|UA-38676921-6 (Universal) +|
|CONTENT GROUP 2||ungrouped|
Since custom dimensions don’t display their names in the tracking calls, I can only compare among accounts to make an educated guess at what most of these dimensions refer to.
For UA-38676921-2, my best guess is that it’s tracking the following:
CD1: Premium (360) or non-Premium GA account
CD4: Number of Properties within the selected Account
CD5: Number of Views within the selected Account
CD12: Industry of the Property
For UA-38676921-4, it’s tracking:
CD4: Number of Accounts within that organization (can be >1 for Premium 360 clients)
CD6: Number of Properties associated with my email address
CD7: Number of Accounts associated with my email
CD8: Number of Views associated with my email
CD13: Industry of the current Property
CD29: Number of Views within the Account
For UA-38676921-6, it’s tracking:
CD1: Yes = Premium 360 Account, No = non-Premium
CD3: Channel (‘Web’ or ‘App’)
CD4: Number of Views within current property
CD12: Industry of the current Property
CD15: 1 = Property linked to Google AdWords, 0 not linked to AdWords
CD16: 1 = Property linked to Google AdSense, 0 not linked to AdSense
CD21: Number of Views within the Account
There’s also one very long string (CD22 and CD37 in UA-38676921-6 and UA-38676921-4, respectively) but it’s unclear what it contains as it’s encoded.
Clicking around reveals what events are being tracked by Google Analytics. All these events appeared to be tracked by all 3 Universal Analytics trackers. These are some of them:
#1 Clicking on a property from the account overview page:
|action||Acquisition Card Tab Switch|
#2 Expanding the left-side menu:
#3 Clicking into the Audience > Geo > Location report
#4 Drilling into the locations report (2 events set simultaneously)
Overall, GA is tracking most interactions on the page that would be useful for improving the user interface: navigation clicks, report dropdowns, drilldowns, export, date changes, etc. They aren’t tracking in crazy detail — quite a few elements like sorting are just grouped into a generic “ec = kpi, ea = performance hit” event. They also aren’t tracking every user interaction like hovers or each movement of the mouse, just clicks that open a report or produce a new view.
GA sets the following groups in the tracking code:
- ungrouped (for Discover, Home, Customization, Admin)
- content (Behavior reports)
- visitors (Audience reports)
- acquisition (Acquisition reports)
- conversions (Conversion reports)
Maybe this was set up correctly at one point, but for now so much of the content is falling into ‘ungrouped’ it doesn’t seem very useful.
Property UA-38676921-4 appears to have the most built-out tracking, and is the only one including custom metrics. For now it’s not clear on what these are actually counting — I’ll update this if I can figure it out.
Google Analytics tracks itself using a fairly conventional implementation. It uses multiple trackers, custom dimensions, custom metrics, events, and tracks a user ID. However it doesn’t use Google Tag Manager, the event tracking is not especially detailed, content grouping wasn’t set up for all pages, the events aren’t named in a particularly logical fashion (imo), there’s no cross-domain tracking, etc. They also aren’t tracking much user detail. That is probably because they can match up that info server-side based on the user ID and their internal clickstream reports, and don’t need to pass it into GA explicitly — in the end I’m sure Google isn’t tracking *less* user data than other sites. So while it was fun to look at Google’s own implementation of Google Analytics, it didn’t really display an especially advanced or well-thought out implementation, and seemed like the tracking has been deteriorating over time. Overall it gives the impression that Google employees aren’t actually using Google Analytics as their primary tool for analyzing usage of Google Analytics, and I suspect most analysis occurs elsewhere.