How a duplicate transaction happens
Most shops fire the purchase event on the order confirmation page — the thank-you screen a customer sees after paying. That page is an ordinary web page, so anything that loads it again fires the event again. A customer refreshing to check the payment went through, pressing back and then forward, bookmarking the receipt, or reopening the same URL from a confirmation email will each produce another purchase in your reports.
Payment gateways make it likelier. When a shopper is redirected out to a bank or wallet and returned to the site, the trip back can pass through the confirmation URL more than once, and a slow connection tempts people to reload rather than wait. Some plugins add to the problem by firing a purchase from the theme template and again through a tag manager, so a single page view records the order from two places.
The defence is a unique order identifier sent with every purchase. GA4 uses the transaction ID to recognise a sale it has already recorded, and Meta uses an event ID for the same job. Without that value the platform has nothing to match on, and every repeat looks like a fresh sale.
Why duplicate transactions matter
Revenue is the figure a business owner checks first, and duplicates inflate it quietly. Nothing in the interface looks broken. The reports simply show more money than the shop actually took, and the gap against the accounting system turns into an argument about which number to believe.
The damage is not confined to reporting. Google Ads and Meta bid towards conversion value, so importing inflated purchases teaches the algorithm that certain campaigns, audiences or products are worth more than they are, and budget drifts towards them. A duplicate problem costs real money, not just credibility.
Where duplicate transactions go wrong
The most common cause I find is a missing or unstable transaction ID — a value regenerated on every page load, or left empty because a developer treated it as optional. Deduplication cannot work on a value that changes between loads.
The second is double instrumentation: a purchase tag hard-coded into the theme while the same tag is also deployed through Google Tag Manager. Both fire, both look correct in isolation, and each carries its own identifier. The third is assuming one platform’s fix covers the others. An order deduplicated properly in GA4 can still be counted twice in Meta if the browser pixel and the Conversions API are not tied together by a shared event ID.
How to fix it
Place a test order, then deliberately reload the confirmation page while watching the realtime report and the tag debugger. If a second purchase appears, you have reproduced the fault in minutes rather than guessing at it. Confirm that the transaction ID is present, unique to the order, and unchanged on every reload of the same receipt.
Then move the trigger away from the fact that a page loaded. Fire the purchase from a state that can only exist once — a one-time flag written when the order is created, or a server-side purchase event sent by the backend, which knows whether that order has already been reported. Finally, reconcile analytics revenue against the shop’s own order list on a regular schedule. That reconciliation is what catches the problem before a client does.
