Multiple analytics scripts are not redundantly loading the same data
Why it matters
When the same tracking script loads twice — typically gtag.js direct plus GA4 nested inside a Google Tag Manager container — every pageview, every event, every conversion fires twice. Real conversion rates look 50% lower than they are, user counts double, session durations break because the same user is hitting consecutive pageviews in millisecond intervals, and automated bidding on ad platforms optimizes against phantom volume. The data contamination is permanent for the affected window.
Severity rationale
Info because redundant scripts corrupt data but the condition is rare and easy to remediate once spotted.
Remediation
Pick one loader for GA4 and remove the other. In app/layout.tsx, keep exactly one of these patterns:
// Option A: direct gtag
<Script src={`https://www.googletagmanager.com/gtag/js?id=${GA_ID}`} />
// Option B: GTM (which itself loads GA4)
<Script src={`https://www.googletagmanager.com/gtm.js?id=${GTM_ID}`} />
If you ship Option B, remove every direct gtag.js tag. For Segment destinations, confirm no downstream destination has its own SDK initialized in the app.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Analytics & Tracking Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from marketing-analytics·automated