Duplicate Tracking Detector
Find duplicate events in your dataLayer or GA4 event list
How It Works
Paste your event data
Copy your dataLayer array or GA4 event list in JSON format and paste it in.
Run the detector
The tool scans for duplicate event names, transaction IDs, and parameter combinations.
Review flagged duplicates
See exactly which events are duplicated and how many times each fires.
Duplicate Tracking Detector
The Hidden Cost of Duplicate Tracking in GA4 and Google Ads
Duplicate conversion tracking is one of the most expensive and hardest-to-detect problems in digital analytics. When a purchase event fires twice for a single transaction, your reported conversion count doubles, your revenue figure inflates, and Google Ads Smart Bidding receives false signals that cause it to over-spend. Businesses with duplicate tracking regularly discover they have been bidding far too aggressively on campaigns that appeared profitable but were actually breaking even.
What Causes Duplicate Tracking in GTM?
- Multiple GTM containers — if two GTM container snippets are present on the same page, every tag fires twice.
- Overly broad triggers — using "All Pages" instead of a specific page match for purchase tags.
- History Change triggers — on SPAs, can fire page_view on initial load AND on every route change.
- Vendor scripts firing independently — some CMS platforms include their own Google Analytics tags alongside your GTM tags.
How to Fix Duplicate Purchase Events in GA4
The most reliable fix is a combination of GTM trigger deduplication and GA4 transaction_id deduplication. In GTM, use a Custom Event trigger that fires only on your specific purchase event name. Set the trigger to fire Once Per Event. In your server-side code, ensure the purchase event push only fires once by setting a session cookie after the first push.