How to prevent duplicate conversions in GA4, Google Ads and Meta
Filed
Baris Asa, Synctag, tracking specialist, London · Last checked:
If GA4, Google Ads or Meta shows more purchases than your store has orders, one sale is reaching the platform twice: two senders deliver it, or a browser copy and a server copy arrive without a shared key. Prevent it with one sender per platform, the order number as the key on every copy (transaction_id for GA4 and Google Ads, event_id for Meta), any server copy built on that same key, a check before every tracking change goes live, and a weekly count against store orders. If GA4 revenue is above Shopify but the purchase count isn’t, it is usually refunds, not a duplicate.
Two words carry this chapter. A sender is anything that delivers a purchase to a platform: a tag, an app, a pixel, a server. The key is the order reference the platform uses to recognise two copies as one sale.
Is it live now? A check you can run yourself. Pick the last full week and count orders, not revenue: refunds change revenue, not the number of orders. First make sure GA4, Meta and the store report in the same time zone, or the edges of the week won’t line up.
- Store: the number of orders for that week (in Shopify, the Orders list filtered by date), minus test and cancelled orders.
- GA4: Explore, a free-form exploration, with the Ecommerce purchases metric for the same dates.
- Meta: Events Manager, your dataset, the Purchase events received for the same dates. Not the Purchases column in Ads Manager: that counts by ad and attribution window, and won’t match orders anyway.
GA4 usually sits a little below the store, because some buyers refuse cookies or block scripts. Once the time zones match, any week where GA4 or Meta is above the store is a duplicate until proved otherwise.
Already seeing it? This chapter is prevention. The diagnosis lives elsewhere:
- GA4 revenue higher than Shopify: every cause, normal and fault, and why refunds don’t reduce GA4 revenue.
- Purchase event fires twice in GA4: F-101 and finding the second sender.
- Meta Pixel and the Conversions API (CAPI, Meta’s server-to-server feed) both counting: F-102 and the Pixel and CAPI note.
Fix the live duplicate there first. If nobody on your side owns the tags, that is the work on the Google Tag Manager consultant page. Then the five rules below keep it from returning after the next app install, theme update or server-side move.
| Rule | Stops | Who |
|---|---|---|
| 1. One sender per conversion | Two tags or apps sending one sale | Tracking |
| 2. Order number as the key | Copies the platform can’t match | Developer |
| 3. Server copy on the same key | Browser plus server both counting | Tracking |
| 4. Check every change | A new app bringing a sender back | Anyone who publishes |
| 5. Weekly count | A duplicate running unnoticed | Revenue owner |
“Tracking” means whoever looks after GA4, Google Tag Manager (GTM) and the ad tags: an agency, a freelancer or an in-house analyst. Rules 1 to 3 are for them. Rules 4 and 5 are yours.
What are the two ways one sale gets counted twice?
Two senders, one platform. The purchase reaches GA4, Google Ads or Meta from two places: a GTM tag and a Google tag hardcoded in the theme, a theme and an app both installing GTM, a second container, or the thank-you page sending again when it is reloaded. Each copy looks like a real purchase. That is F-101 .
Two paths, no shared key. The browser sends the purchase and a server sends it too, on purpose, so the platform still gets sales the browser loses. The platform merges the two only when both carry the same key. Without it, both count. That is F-102 .
Both come from the same gap: nobody wrote down who sends what, with which key. Rules 1 and 2 are that record.
Rule 1: who is allowed to send each conversion?
One named sender per conversion per platform, on record in a sender register kept with the tracking documentation. Every sender uses the order number as its key (Rule 2). Exhibit A: a register for a Shopify store with a server-side container (illustrative, not a client).
| Conversion | Sender | Switched off |
|---|---|---|
| GA4 purchase | One GTM tag | Theme gtag, app’s GA4 |
| Google Ads purchase | GTM tag, plus server copy | GA4 import as primary |
| Meta Purchase | Pixel in GTM, CAPI from server | App’s Pixel, second CAPI |
The last column matters most. It names the routes that will try to come back: the app that offers to “connect Google Analytics” during setup, the theme snippet from an earlier agency, the platform’s own integration. On Shopify, Google and Meta can each be connected through a sales channel app, a custom pixel in Customer Events (Shopify’s settings page for tracking code), theme code or GTM. Pick one per platform, write it down, and switch the others off.
One browser sender plus one server sender, sharing a key, is a design. Two browser senders is a fault, even on the days the key happens to absorb it.
Rule 2: which key does each platform deduplicate on?
Each platform merges copies of one sale on its own key, and the rules differ.
| Platform | Key | Merges | Watch for |
|---|---|---|---|
| GA4 | transaction_id | Two purchase events with the same ID; no window published | Empty ID |
| Google Ads | transaction_id | Two conversions with the same ID on the same action | A second action |
| Meta | event_id and event name | A Pixel and a CAPI copy with both matching, the second within 48 hours of the first | Two server copies |
What each “watch for” means:
- GA4, empty ID. Google says GA4 deduplicates all purchase events sent with an empty transaction_id. Real orders collapse into one, so you undercount.
- Google Ads, a second action. The ID only merges copies on the same conversion action. A primary action is one Google Ads counts in its Conversions column and bids on. Actions created through the Google Analytics interface start as secondary. But an imported GA4 purchase made or switched to primary in Google Ads, next to a primary Google Ads tag, counts the sale twice, and no transaction_id merges them. Keep one primary purchase action. The counting settings are F-104 .
- Meta, two server copies. Meta documents merging a Pixel copy with a Conversions API copy. Don’t count on it merging two server copies of one sale. Keep one server connector.
So design the key once, at the order:
- Use the order number. Created when the order is created, passed unchanged to every tag and every server event. GA4, Google Ads and Meta can all take the same string.
- Make it exact. Google Ads names prefixes, suffixes and extra spaces as reasons a match fails, and allows up to 64 characters. Meta asks for an identical event name as well as an identical event_id, so treat Purchase and purchase as two names.
- Never empty, never reused, never random per fire. An ID reused across orders makes GA4 and Google Ads drop genuine sales. A random ID made fresh by each tag means no two copies ever match.
The key catches a duplicate the register missed. It doesn’t replace the register. Meta only merges copies that arrive within 48 hours of each other, and there is no published window for GA4, so don’t rely on the key to absorb a sender you could remove.
Rule 3: how do you add a server path without doubling?
Key first, server second. The F-102 cases I see usually start the day the Conversions API or a server-side container goes live. The server copy was built before anyone checked what the browser sends.
- Fix the key on the browser copy. The Pixel sends event_id and the Google tags send the transaction ID, both from the order number. Check one test order in the browser’s DevTools, Network panel (the list of requests the page sends), or in Tag Assistant: eid on the Meta request, the transaction ID parameter on the GA4 collect request (usually shown as ep.transaction_id), and oid on the Google Ads conversion request.
- Build the server copy on the same key. The server event reads the same order number, not a value it makes up. Same event name, same conversion action.
- Test both copies on one order. For Meta, Test Events in Events Manager shows the browser and server copies; how to prove the event_id matches has the full check. For Google Ads, Goals, Summary, Diagnostics may show a Multi-source conversions card, which flags an overcount when fewer than 10% of transaction IDs matched between the tag and the extra source over two days. It is a beta feature and not on every account.
- Switch off the old sender in the same release. Shopify’s own migration advice: connect the new pixel after removing the old one if you want to avoid duplicate tracking. Remove old code from theme files too, and from checkout Additional scripts on any store still running them (what changed when those went).
Whether a server path is worth adding at all is a separate question: server-side tracking.
Rule 4: which changes bring a second sender back?
A clean setup stays clean until someone changes something. These put a second purchase sender live:
- Installing a sales channel or marketing app that offers to connect GA4, Google Ads or Meta for you.
- A new theme, or a theme update, carrying a hardcoded tag or a second GTM snippet.
- A copied tag in GTM. A duplicated purchase tag left live, or a second trigger added to the original.
- A GA4 “Create event” rule. Creating an event in GA4 copies an existing one and leaves the original running. A rule that creates purchase from the thank-you page view, next to a tag already sending purchase, makes two.
- Moving to Shopify Customer Events. A custom pixel goes live while the old theme code still runs.
- A new agency’s container added beside the old one instead of replacing it.
- Server-side go-live before the browser key is fixed (Rule 3).
- Importing GA4 conversions into Google Ads as primary next to the Google Ads tag.
The check is short. Any change that touches a tag, a pixel, an app or a container is checked against the sender register before it is published. Afterwards, place one test order in a fresh browser session, with GTM’s Preview mode closed so you see what real visitors send, and count the purchase requests in the Network panel: one per platform from the browser. If the change adds a sender, the register changes first, with a date and a reason.
In my experience the second sender is rarely something new. It’s something old nobody removed.
Rule 5: how do you check the count against the store?
Once a week, on the last full week, by whoever owns the revenue number. The first two checks need no technical help.
- GA4 against the store (you). The check at the top of this chapter. Once time zones match, any week above the store is a duplicate until proved otherwise.
- Meta against the store (you). Purchase events received in Events Manager against real orders. If Meta is above, open the Purchase event’s details: it shows whether events arrive from the browser, the server or both, and how many were deduplicated. Use the count against orders as the test. A deduplication percentage on its own proves little.
- Transaction IDs in GA4 (tracking). In a free-form exploration, Transaction ID against Ecommerce purchases. A (not set) row with purchases, or two ID formats side by side, means a sender without the key.
- Google Ads (tracking). Google Ads doesn’t report transaction IDs, so check the setup instead. One primary purchase action, no more. Purchase conversions for the week, by conversion time, set against store orders: the ads can’t have driven more orders than the store took. And Goals, Summary, Diagnostics for a “Google tag is missing transaction ID” alert, which means the tag isn’t passing the order number.
Write the result down each week. A gap that jumps the week after a change points at that change. Keeping one written definition for each number people trust is the reporting chapter.
What doesn’t this prevent?
These rules stop one sale being counted more than once. They don’t fix:
- Refunds. Shopify takes refunds off its sales. GA4 keeps the purchase unless a refund event is sent, so GA4 revenue can sit above Shopify with no duplicate at all: GA4 revenue won’t drop after refunds.
- The wrong events counted as conversions, or the Count setting wrong for the action: F-104 .
- A wrong value on a single purchase: tax, shipping, currency. That’s F-302 .
- Missing purchases or empty items: the opposite error, F-301 .
- GA4 and Google Ads disagreeing for normal reasons: GA4 and Google Ads numbers don’t match.
Common questions
How do I set up GA4 so each purchase counts once?
Keep one sender for the purchase event, and send the order number as transaction_id on it. GA4 deduplicates purchase events with the same transaction ID, so a resend carrying the same ID is dropped. A second sender with no ID, or a different one, is counted. If it is already happening, the fix is F-101.
How do I set up the Meta Pixel and CAPI so each purchase counts once?
Send the same event_id and the same event name on the Pixel copy and the Conversions API copy, with the event_id built from the order number so both read the same value. Meta merges the pair only if the second copy arrives within 48 hours of the first. Keep one server connector. If Meta is already double counting, the fix is F-102.
Does Google Ads deduplicate conversions automatically?
Only on the transaction ID, and only within the same conversion action. Google Ads treats a second conversion with the same action and the same transaction ID as a duplicate and doesn’t count it. A GA4-imported purchase is a separate action, so if it is primary next to the Google Ads tag, the sale counts twice. Keep one primary purchase action.
Is the Count setting in Google Ads a way to prevent duplicates?
No. Google says adding a transaction ID is not the same as changing Count. Count One allows one conversion per ad click; the transaction ID stops the same order counting twice. For ecommerce, send a unique transaction ID and keep Count on Every, so two real orders from one click both count.
What should the transaction ID be?
The store’s order number, created when the order is created and passed unchanged to every tag and server event. Never empty, never reused across orders, never generated fresh by each tag. Up to 64 characters for Google Ads, and exactly the same string on every copy, with no added prefix or spaces.
How often should I check for duplicate conversions?
Weekly, on the last full week: GA4 Ecommerce purchases and Meta Purchase events against store orders, with time zones matched. Check Google Ads has one primary purchase action and no missing transaction ID alert. And once after every change to a tag, app, pixel or container, with a single test order counted in the Network panel.
Also filed as
- how to prevent duplicate conversions
- deduplicate conversions across platforms
- same order id for transaction_id and event_id
- shopify custom pixel duplicate tracking
- conversion deduplication best practice
- transaction_id and event_id deduplication
- google ads duplicate conversions transaction id
Faults explained here
- F-101 Duplicate conversion firing Purchases counted twice: revenue inflated on Meta, and in GA4 and Google Ads once transaction_id goes missing or changes per fire. ROAS looks great, until finance disagrees.
- F-102 Platform signals not deduplicated Meta and Google report more conversions than actually happened. The browser hit and the server hit both claim the same sale.
Sources
- Analytics: Minimize duplicate key events with transaction IDs (deduplicates purchase events with the same transaction ID; no time window stated; don't send an empty string, all empty-ID purchases are deduplicated; don't reuse an ID across users; app streams send it via the Firebase SDK; checked 16 Nov 2026)
- Google Ads: Use a transaction ID to minimize duplicate conversions (same conversion action and transaction ID: the second is a duplicate; up to 64 characters; prefixes, suffixes or extra spaces break the match; not the same as the Count setting; the transaction ID parameter is typically oid in the request; transaction IDs won't be reported in Google Ads; a 'Google tag is missing transaction ID' diagnostic means the tag isn't passing advertiser-assigned IDs; checked 16 Nov 2026)
- Google Ads: Create conversions from Google Analytics events (conversion actions created through the Google Analytics interface are set as secondary; Conversions column counts primary actions only; checked 16 Nov 2026)
- Google Ads: Multi-source conversions diagnostics (beta; Goals, Summary, Diagnostics; alert when fewer than 10% of transaction IDs matched between the Google tag and the additional source in the past 2 days; checked 16 Nov 2026)
- Meta for Developers: Handling duplicate Pixel and Conversions API events (a Pixel's eventID must match the Conversions API event_id, and event must match event_name; within 48 hours of the first event with that event_id; the first received is generally preferred; checked 16 Nov 2026)
- Shopify: Migrating to custom pixels (tracking the same event more than once is a common migration issue; connect the new pixel after removing the old one to avoid duplicates; remove old code from liquid files and checkout Additional scripts; checked 16 Nov 2026)
- Analytics: Create or modify key events (creating an event copies an existing event without changing the original; modifications overwrite existing events; checked 16 Nov 2026)
When GA4, Google Ads or Meta counts more purchases than the store has orders, Baris Asa, a London tracking specialist working as Synctag, finds the second sender and fixes the key, then leaves a written sender register your team keeps. For ecommerce brands and the agencies behind them.
Google Tag Manager consultant →