How to fix duplicate and double-counted conversions in GA4
Double-counted conversions are insidious: they make your ROAS look fantastic while quietly making your data worthless. If your GA4 numbers keep drifting above your real sales, duplication is the usual cause. Here are the common sources and how to fix each one.
Why duplicates happen
A conversion gets counted more than once whenever the same event is sent by more than one source, or fires more than once, without anything to deduplicate it. On a typical site there are several tags that all think it’s their job to report the purchase, and nothing telling GA4 they’re the same sale.
The common causes
- Multiple tags for one event: a native integration, an app or plugin, and a hand-added tag all firing the purchase.
- No transaction_id: without a unique ID, GA4 can’t tell two reports of the same order apart.
- Thank-you page refreshes or back-button: the purchase event re-fires when the confirmation page is reloaded.
- Pixel and server-side both firing without a shared event ID (the deduplication trap for Meta CAPI and GA4 alike).
- Conversion marked on multiple events, so one journey counts several times.
Is GA4 over-counting your conversions?
We’ll scan your live tags for duplicates and double-firing. Free, 10 seconds, no signup.
Check my tracking freeHow to find them
Use GA4’s DebugView or real-time reports and complete a test purchase: you should see exactly one purchase event. If you see two, note what’s firing. Then compare GA4’s conversion count against your platform’s actual orders over the same period; a consistent overcount points straight at duplication.
How to fix them
- Send one purchase event from a single source of truth, ideally via GTM and the dataLayer.
- Always include a unique transaction_id.
- Set the conversion on the right single event, not several.
- For pixel-plus-server setups, use a shared event ID so browser and server versions deduplicate.
- Guard against re-fires on page reload.
Fixed properly, GA4 and your real sales land within a few percent and stay there, and you can trust your ROAS again.
Get duplicate conversions found and fixed
We track down every duplicate and deduplicate your setup so your numbers are real. The audit comes off any build.
See how it works & pricingRelated guides
GA4 ecommerce tracking Meta Conversions API explained Why GA4 and Shopify don’t match PricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Ads, Meta and server-side tracking. See pricing · All guides · Back to datahound.agency
Duplicate conversions: common questions
Why is GA4 showing more conversions than I actually got?
Usually duplication: the same purchase is being reported by more than one tag, or firing more than once, with nothing to deduplicate it. Missing transaction IDs and multiple purchase tags are the usual culprits.
How do I check for duplicate conversions in GA4?
Do a test purchase with GA4 DebugView or real-time open; you should see exactly one purchase event. More than one means duplication. Comparing GA4’s counts against your real orders over time also reveals a consistent overcount.
How do I stop conversions double-counting?
Send one purchase event from a single source with a unique transaction_id, set the conversion on just one event, and for pixel-plus-server setups use a shared event ID so the browser and server versions deduplicate.