Tracking Audit Tool: Check GTM, GA4 & Consent Mode

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), conversion IDs (AW-XXXXXX) and whether gtag.js runs alongside GTM, a classic cause of double counting.
• Consent Mode: Whether a default consent call precedes the tags and which signals are set. Mandatory for advertisers in the EU since Consent Mode v2.
• Consent platform: Detection of common CMPs like Usercentrics, Cookiebot, Borlabs, Complianz or OneTrust.
• Other pixels: Meta Pixel, TikTok, LinkedIn Insight, Pinterest, Microsoft/Bing UET and Hotjar/Clarity.
• Server-side hints: If gtm.js loads from your own subdomain instead of googletagmanager.com, that points to a server-side setup.

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.