10 Common Analytics Tracking Mistakes That Silently Corrupt Your Data
Bad tracking is worse than no tracking, because bad data still looks confident on a dashboard. Teams make real decisions off numbers that are quietly wrong by 20-40%, and they rarely find out until a much bigger discrepancy — like ad spend not matching reported conversions — forces an audit. Here are the mistakes that cause it most often, and how to catch each one.
1. Duplicate or Conflicting Tracking Tags
The single most common issue: the GA4 tag fires twice because it's hard-coded in the site template and also added through Google Tag Manager. This inflates pageviews and sessions without any obvious symptom. Check with Tag Assistant or GTM's Preview mode — if you see two GA4 hits firing per page load, you have this bug.
2. Not Filtering Internal and Bot Traffic
Your own team, your agency, and automated bots can meaningfully skew small-to-midsize sites' numbers. In GA4, set up an internal traffic filter under Admin > Data Streams > Configure Tag Settings, and enable "Exclude all hits from known bots and spiders" in the same area — it's off by default in some configurations.
3. Conversion Events That Fire on the Wrong Trigger
A "purchase" event tied to a "thank you" page URL will keep firing if a user refreshes that page or navigates back to it, inflating conversions. Tie conversion events to a one-time trigger — a dataLayer push fired only on successful transaction completion — rather than a page view.
4. Cross-Domain Tracking Left Unconfigured
If checkout or booking happens on a different domain or subdomain than your main site, unconfigured cross-domain tracking will split what should be one session into two, breaking attribution and making conversion rate look artificially low. Configure it under GA4's Admin > Data Streams > Configure Tag Settings > Configure your domains.
5. UTM Parameters Applied Inconsistently
Capitalization and naming inconsistency (facebook vs. Facebook vs. FB) fragments a single channel into multiple rows in your reports. Standardize a UTM naming convention document and enforce it for every campaign, every time, with no exceptions from any team member.
6. Sampling and Thresholding Hiding Real Numbers
GA4 applies data thresholding to protect user privacy on demographic and interest reports, which can make numbers disappear entirely in certain breakdowns on lower-traffic properties. This isn't a bug — it's expected — but teams often mistake missing numbers for a tracking failure when it's actually a privacy safeguard.
7. Not Testing After Every Site or CMS Update
A redesign, a CMS migration, or even a page builder plugin update can silently strip tracking codes from templates. Run a tag audit with Tag Assistant after every deploy that touches templates, not just after major launches.
8. Ecommerce Tracking Missing Enhanced Data
Basic purchase tracking without item-level data (product ID, category, price, quantity) throws away most of GA4's ecommerce reporting value. Implement enhanced ecommerce events through GTM's datalayer so product performance reports actually populate.
9. No Data Retention or Backup Plan
GA4's default data retention for event-level data is 14 months unless changed in Admin > Data Settings > Data Retention. Extend it to the maximum available, and export critical historical data to BigQuery or Looker Studio if you need it beyond that window.
10. Nobody Owns Tracking QA
Building a Tracking QA Checklist
Turn the ten issues above into a recurring checklist rather than a one-time cleanup. Run it after every major site change, on a quarterly schedule at minimum: verify tag firing with Tag Assistant, confirm conversion events trigger only once per real action, check that internal traffic and bot filters remain active, and spot-check that revenue or lead-value data still matches your source-of-truth system within an acceptable margin. A five-minute checklist run quarterly prevents the multi-week data-trust rebuilding project that follows a discovered tracking failure. For a deeper look at this, see our guide, Sitemaps, Robots.txt & Canonicalization.
The root cause behind every mistake above is usually the same: no single person is responsible for auditing tracking health. Assign explicit ownership and run a quarterly tracking audit — checking tag firing, event parameters, and conversion accuracy — as a standing calendar item, not an afterthought. For a deeper look at this, see our guide, Title Tags, Meta Descriptions & Headers.