What the tracking audit finds
- Google Tag Manager: All container IDs (GTM-XXXXXX) in the source code, including a duplicate warning when the same container is embedded more than once.
- GA4 and Google Ads: Measurement IDs (G-XXXXXX), Google tag IDs (GT-XXXXXX), conversion IDs (AW-XXXXXX), Floodlight (DC-XXXXXX) and whether gtag.js runs alongside GTM, a classic cause of double counting.
- Consent Mode: Whether a default consent call precedes the tags, whether all four v2 signals are set and whether the default is denied. Mandatory for advertisers in the EU since Consent Mode v2. More on our Consent Mode v2 page.
- Consent platform: Detection of common CMPs like Usercentrics, Cookiebot, Borlabs, Real Cookie Banner, Complianz, OneTrust, CookieYes or Didomi.
- Other pixels: Meta Pixel, TikTok, LinkedIn Insight, Pinterest, Microsoft/Bing UET, Snap, Reddit, X, Criteo plus Hotjar, Clarity and Matomo. Detected by script addresses and init calls, not by loose keywords.
- Server-side hints: If gtm.js loads from your own subdomain or via a path on your own domain (Google tag gateway), that points to a server-side setup. We also detect custom loaders, for example from Stape, even when the container ID is obfuscated.
When you should look more closely
Two GTM containers on one page, gtag.js next to GTM, or marketing pixels firing in the source code before consent: those are the three findings that most often cost real money or real trouble in our audits. We have been cleaning up setups like these since 2006. What a full audit covers, including dataLayer and server-side, is on our Tracking & Analytics page. Head straight to a free intro call via contact.