GA4 counting the same order twice? Fix your transaction ID
Short answer: If GA4 shows more purchases or more revenue than your shop's own order list, the usual causes are a thank-you page that sends the purchase event every time it's loaded, two tags or plugins both sending purchases, or a purchase event with a missing, empty or fixed transaction ID. Google Analytics deduplicates purchase events that share the same transaction ID, so the first fix is to send your real order number as transaction_id on every purchase. Then remove the duplicate sources so you're not relying on deduplication alone.
Spotting the problem
Some difference between GA4 and your shop is normal: ad blockers, people declining consent and failed page loads mean GA4 usually sees fewer orders, not more. More purchases in GA4 than in your shop is a sign of duplicates.
To check:
- Pick a few days and export orders from your shop system.
- In GA4, build an exploration with the transaction ID dimension and the purchases metric for the same dates.
- Look for transaction IDs that appear with a purchase count above 1, blank IDs, or the same ID on many different days.
What you see tells you which fix you need.
Why purchases get counted twice
The thank-you page fires on every load
The most common cause. The purchase event is sent when the order confirmation page loads. If the customer refreshes it, comes back to it from their browser history, or opens the link in their confirmation email that leads back to that page, the event fires again.
Two sources sending the same event
A shop platform's built-in GA4 integration plus a separately installed tag, a plugin plus Google Tag Manager, or a server-side setup plus a browser tag can each send their own purchase event. Each is "correct" on its own.
Missing or broken transaction IDs
Google's help page on transaction IDs says you must add one to every ecommerce event to deduplicate transactions and properly process refunds. Problems arise when:
- no
transaction_idis sent, so there's nothing to deduplicate on - the value is an empty string; Google warns that GA4 will deduplicate all purchase events with an empty transaction ID, so you lose orders instead of gaining them
- the tag sends a fixed placeholder for every order; Google warns this can "significantly undercount" key events
How transaction IDs fix it
The GA4 developer guide shows the purchase event carrying transaction_id alongside value, currency and items. Google's help page explains that if two purchases are registered with the same transaction ID, Analytics deduplicates them.
Rules for the ID, from the same page:
- Unique for each order. Your order confirmation number is the natural choice.
- Dynamic. It must change with every order, filled from your shop's data on the confirmation page.
- No personal information. The ID mustn't contain anything that identifies an individual customer, such as an email address.
- Not shared across customers. The same ID shouldn't be used by different users.
For apps, Google notes that transaction IDs should be sent through the Firebase SDK.
Stop the extra events at the source
Deduplication is a safety net. Fixing the cause makes your data easier to trust:
- Fire the purchase event once per order. Have your server mark the order as "tracked" when the confirmation page first renders and skip the event on later loads. Some platforms do this with a flag; others need a small code change.
- Choose one sender. Decide whether your platform integration, your tag manager or your server-side setup sends purchases, and switch the others off for that event.
- Check the confirmation link in emails. If it points to the thank-you page, point it to the customer's order page instead.
- Test in DebugView. Place a test order, refresh the confirmation page, and confirm only one purchase arrives with the right transaction ID.
Payment pages that send customers back twice
Some payment providers return the customer to your site after paying, and some also redirect a second time after extra verification. If both returns land on the confirmation page, that's two page loads for one order. Check the return URLs in your payment settings and make sure only one of them leads to the page that sends the purchase event.
Don't forget refunds
The GA4 ecommerce guide also describes a refund event that uses the same transaction_id. With consistent IDs, you can send refunds so revenue reports reflect returns, and it's easier to match GA4 rows to orders when you investigate.
What about past data?
Fixing the tags only affects new data. For reports covering the period with duplicates, note the date the fix went live, and compare shop totals and GA4 totals before and after. If you report revenue to anyone else, state the issue and the date range rather than mixing inflated and corrected months without comment.
A worked example
An illustrative York tea shop saw GA4 revenue noticeably higher than its shop dashboard for a whole quarter. An exploration showed many transaction IDs with two or three purchases each. The shop had installed a GA4 plugin while an older tag manager container still sent purchases, and customers often refreshed the confirmation page to check their order. The owner disabled the tag manager's purchase tag, kept the plugin, confirmed it sent the order number as transaction_id, and asked the developer to fire the event only on the first page load. Within a week, GA4 purchases were slightly below the shop's order count, as expected.
FAQ
Should GA4 ever show more orders than my shop?
Rarely, and not by much. Consistently higher numbers almost always mean duplicates.
Can I use the same transaction ID for a reorder?
No. Each order needs its own ID, or GA4 may treat the second order as a duplicate of the first.
Will fixing this change my ad platform conversions?
Only if those platforms read from the same tags. Check each one's own duplicate settings separately.
Is the transaction ID personal data?
It shouldn't be. Use an order number that doesn't contain names or email addresses.
If your analytics revenue doesn't match your shop, send us a sample date range and we'll find where the extra purchases come from.