Two tags doesn't mean double the data — it means broken data.
We scan the page for multiple loads of gtag.js, multiple gtag('config') calls with the same measurement ID, leftover Universal Analytics code (ga.js, analytics.js), and Google Tag Manager containers running alongside standalone gtag implementations.
When two analytics tags fire on the same page, every page view, every click, and every conversion gets counted twice. Bounce rate looks impossibly low. Session duration looks impossibly high. Conversion rate looks fantastic — and decisions based on those numbers are wrong in the opposite direction of reality.
A Shopify store installs a GA4 app, but the previous developer hard-coded gtag.js in theme.liquid. Both fire on every page. The brand's reported revenue is 2x reality — they raise ad budgets thinking ROAS is great, then bleed cash for two quarters.
A SaaS company has GA4 set up in Google Tag Manager AND a hard-coded snippet from before GTM was added. Every signup conversion fires twice. Sales is told signups are up 80%, hires more reps, then watches the inflated number collapse when it's fixed.
A franchise's marketing manager installs GA4 manually, not realizing the corporate template already includes it. Every page view doubles. Customer journey reports show people 'visiting' locations they never actually went to — leading to wrong staffing decisions.