GA4 Event Deduplication: Preventing Double-Counting in Your Reports

The most common source:two GA4 implementationsrunning simultaneously

The single most common cause of event duplication is two separate GA4 implementations sending data to the same property. This produces exactly double the event count for every interaction. Common configurations that create this:

• Google Site Kit plugin plus a separate GTM container both deploying GA4 to the same property
• A hardcoded gtag.js snippet in the theme header plus a GTM-based GA4 Configuration tag
• An ecommerce plugin's built-in GA4 integration plus a manual GTM implementation
• A legacy Universal Analytics tag that survived migration with a GA4 Measurement ID substituted in

These overlaps are easy to introduce during a re-platform. OurGTM and GA4 configuration guidewalks through how to set up a single, owned source of truth for your GA4 tags.

Diagnosis: in Tag Assistant or GTM Preview mode, load your site and count how many times the GA4Measurement IDappears in outbound requests to google-analytics.com. One request per page load is correct. Two requests indicate duplication.

Purchase event deduplicationvia transaction_id

GA4 has a built-in deduplication mechanism for purchase events: thetransaction_idparameter. Google documents that purchase deduplication with transaction IDs works for data collected throughweb streams. If two purchase events are registered with the same transaction ID, Analytics deduplicates the purchase. For a deeper look at the required fields and formats, see our breakdown ofGA4 purchase event parameters.

That does not mean every double-fire scenario is safe. Deduplication is a protection for purchase events, not a general guarantee that any duplicate architecture is fine. Teams should still remove duplicate sources where possible and validate the live payloads carefully.

Common failure points are simpler than many teams think: missing transaction IDs, inconsistent IDs between implementations, or an empty string. Google specifically warns not to sendtransaction_id="", because Analytics will deduplicate all purchases that share that empty value.

Custom event deduplication

GA4 does not natively deduplicate custom events other than purchase. If your form submission event fires twice because two different implementations track the same user action, GA4 counts both unless your implementation prevents the duplicate.

For custom events where deduplication is needed, the solution is at the implementation level: disable the conflicting tracking rather than trying to deduplicate in GA4.

Single page applicationdouble page view

On SPAs, the combination of Enhanced Measurement page view detection (which listens to history state changes) and a custom GTM page_view implementation both firing on route changes is a common source of doubled page views and inflated session counts. The fix is to use one intentional page-view strategy and verify it in the browser usingGA4 debug modebefore pushing live.

Detecting duplication withbigquery

The most precise way to detect event duplication is in BigQuery. Count the number of event rows per transaction_id for purchase events. If any transaction_id has more than one row in the events table, investigate. Similarly, count page_view events per session. If the average page_view count per session is double what you would expect based on your page depth metrics, you have session-level page view duplication. If the duplication has masked the opposite problem, our guide onfixing missing revenue on purchase eventsexplains how to reconcile against your back-office numbers.