10 GA4 Tracking Mistakes Costing You Data (And How to Fix Them)
The most common GA4 implementation errors that silently corrupt your analytics data. Learn how to identify and fix each one.
Most GA4 implementations have at least 3-4 of these issues. Each one silently degrades your data quality, leading to wrong decisions.
1. No Consent Mode Implementation
The problem: Firing GA4 before getting user consent violates GDPR/CCPA and risks massive fines.
The fix: Implement Google Consent Mode V2. Set `ad_storage` and `analytics_storage` to `denied` by default, then update on consent.
gtag('consent', 'default', { 'analytics_storage': 'denied', 'ad_storage': 'denied', 'wait_for_update': 500 });javascript
2. Duplicate GA4 Tags
The problem: Both gtag.js AND GTM are loading GA4, doubling your page views and inflating metrics.
The fix: Pick one method. If using GTM, remove the hard-coded gtag.js snippet. Use GTM's GA4 Configuration tag instead.
3. Missing Enhanced Measurement Events
The problem: GA4's Enhanced Measurement is turned off or partially configured, missing automatic scroll, outbound click, and file download tracking.
The fix: Go to Admin → Data Streams → Enhanced Measurement and enable all relevant toggle switches.
4. No Cross-Domain Tracking
The problem: If your checkout is on a different domain (e.g., Shopify checkout), GA4 treats the return visit as a new session from a referral.
The fix: Configure cross-domain measurement in your data stream settings. Add all your domains to the list.
5. Not Filtering Internal Traffic
The problem: Your team's visits inflate metrics and skew conversion rates.
The fix: Define internal traffic rules in Admin → Data Streams → Configure Tag Settings → Define Internal Traffic. Then create a data filter to exclude it.
6. Default Data Retention (2 Months)
The problem: GA4 defaults to 2 months of user-level data retention. After that, your Explorations reports lose granularity.
The fix: Change to 14 months in Admin → Data Settings → Data Retention.
7. No Conversion Value Assignment
The problem: Conversions are tracked but without monetary values, making ROI calculation impossible.
The fix: Assign values to key events. For lead gen, estimate the value of a lead. For ecommerce, the purchase event should pass the actual revenue.
8. Broken Ecommerce DataLayer
The problem: The `purchase` event fires but with incorrect or missing `items` array, `transaction_id`, or `value`.
The fix: Validate your dataLayer pushes against the [GA4 ecommerce spec](https://developers.google.com/analytics/devguides/collection/ga4/ecommerce). Every purchase event needs `transaction_id`, `value`, `currency`, and an `items` array.
9. Ignoring DebugView
The problem: You deployed tracking changes but never verified them in real-time.
The fix: Use GA4 DebugView (Admin → DebugView) with the Chrome GA4 Debug extension to validate every event fires correctly with proper parameters.
10. No UTM Discipline
The problem: Marketing teams use inconsistent UTM parameters (`facebook` vs `Facebook` vs `fb`), fragmenting traffic source reporting.
The fix: Create a UTM naming convention document and use a UTM builder tool. Standardize on lowercase, hyphenated values.
Catch All 10 Automatically
Our AI-powered audit catches all of these issues and more. Run a free audit →
Check your GA4 implementation
Run a free AI-powered audit to see how your tracking stacks up.
Start Free Audit