GA4

    Duplicate Transactions in GA4: How to Find Them and Stop Them

    Qudees Kiani, founder · · 8 min read

    Short answer

    GA4 removes a repeated purchase with the same transaction ID, on web streams only. Google frames it as removing one user's repeats and gives no time window. To find duplicates, open the Transactions report and sort by E-commerce purchases: any order ID above 1 was counted more than once. The fix is in your tags, not in GA4.

    On this page
    Cover: 5 orders. 11 purchases in GA4.

    Google says GA4 removes duplicate purchases that share a transaction ID. Between 1 and 30 October, a European online store we audited had 229 orders in GA4 and 235 purchases. Five orders were counted 11 times between them, adding about €1,250 of revenue that never happened, if each copy carried the full order value. Google's rule has conditions, and most duplicates slip past at least one of them. This guide covers what GA4 removes and what it doesn't, how to find duplicates in two minutes, the usual causes and how to stop them.

    What GA4 does with a repeated transaction ID

    Google's help page is short: GA4 "deduplicates purchase events with the same transaction ID", and Google gives the purpose as removing "transactions from the same user". In practice:

    • Same transaction ID. If a second tag sends the order number while the first sends a checkout ID, GA4 sees two different purchases.
    • Probably the same user. Google frames the rule around one user's repeats and doesn't say whether a copy from another browser or device is removed. Our reading: don't count on it.
    • Web streams only. Google says the deduplication doesn't apply to app streams.

    Google doesn't say within what time a repeat is removed, or whether the Event count metric and the BigQuery export keep the repeats. Any window you read elsewhere, 30 seconds or a day, doesn't come from Google. For server copies sent through Google's Data Manager API, Google says GA4 keeps the first copy it receives. One rule is clear and easy to break: never send an empty transaction ID. Google says it "will deduplicate all purchase events that have transaction_id=\"\"", so real orders collapse into one.

    Pick the right metric

    GA4's Transactions metric also counts refunds and app subscription events. E-commerce purchases counts only the purchase event, so use that one when you check each order ID.

    What it looked like in one store

    Table of five orders that GA4 counted two or three times each, with the extra revenue they added(opens the full-size image in a new tab)
    Real dataGA4's Transactions report, 1 to 30 October 2026. Order IDs replaced with letters.

    The store's GA4 property recorded 235 purchases and €50,337 of revenue for 229 order IDs. One order appeared three times and four appeared twice: 6 purchases and about €1,250 that didn't happen, assuming each copy carried the order's full value. That is 2.5% of the period's revenue, and every purchase-based number inherits it: purchases, revenue, conversion rate and any return on ad spend calculated from GA4.

    The details point to where they came from. All three copies of the worst order arrived on the same day, all on mobile, in at least two different sessions. GA4 didn't remove them, so either it didn't treat them as one user's repeat, or its rule has limits Google doesn't describe. That pattern fits a confirmation page loaded more than once, for example after a payment app hands the buyer back to the store.

    How to find duplicates in two minutes

    1. Open the Transactions report: Reports, then Monetization, then Transactions. If it isn't there, add it from the Library.
    2. Set a date range of 30 to 90 days and sort by E-commerce purchases, highest first.
    3. Read the top rows. Any transaction ID with a count above 1 was counted more than once. Add up the extra copies and their revenue.
    4. Look for a (not set) row. Purchases without a transaction ID can't be deduplicated at all, and shouldn't exist.
    5. Add a second dimension, such as Device category or Session source / medium, to see whether the copies came from the same device or session.
    6. For a big store, build an exploration: Free form, rows Transaction ID, values E-commerce purchases and Purchase revenue, filtered to the purchase event, with the maximum number of rows.

    Two things can hide repeats. With many order IDs, GA4 can lump rare values into an (other) row, more often when you add a secondary dimension. If you see one, remove the extra dimension or shorten the date range. And explorations only reach back as far as your data retention setting: two or fourteen months on a standard property, longer on Analytics 360.

    Diagram of three ways one order reaches GA4 twice and whether GA4 removes the copy in each case(opens the full-size image in a new tab)
    DiagramThree ways one order reaches GA4 twice. Only the first is the case Google's rule is written for.

    The usual causes

    CauseHow to spot itWill GA4 remove the copy? (our reading)
    The confirmation page loads again: a reload, the back button, an email linkSame ID, same device, minutes or hours apartSometimes, if it's the same user
    The buyer comes back from a payment app in another browserSame ID, mobile, a new sessionUsually not: it looks like another user
    Two setups send the purchase, such as a platform app and Tag ManagerTwo ID formats for one order, or two purchases a few seconds apartNo, if the IDs differ
    A browser tag and a server send the same purchaseCopies with different sources or no session dataOnly if the ID matches exactly
    A trigger fires twice, such as on a page view and a data layer eventTwo copies with the same timestampSometimes, if it's the same user
    Random or session-based IDsIDs that don't match your order numbersNo: every copy looks new

    On Shopify, the thank-you page is now a one-time page, while customers can revisit the order status page as often as they like. A purchase tag that fires on page views there will count again. Shopify's own checkout_completed event fires once per checkout, so a custom pixel that sends purchase only from that event shouldn't repeat. Since July 2026, the Google & YouTube app also sends the purchase from Shopify's server, and Google says it deduplicates that copy against browser events. It doesn't say that covers a purchase tag of your own, so a second tag can still double count. Our guide to GA4 against Shopify covers the rest of that comparison.

    Myth

    GA4 removes duplicate transactions automatically.

    Reality

    Only for repeats with the same ID on a web stream, which Google describes as coming from the same user, with no time window. In the store above, 5 orders were still counted 11 times.

    How to stop them

    1. Use one stable order ID everywhere. The same value, in the same format, from every tag and every server that sends the purchase. Never an empty string, a timestamp or a random number.
    2. Keep one sender per destination. Choose either the platform's app or your own tags for GA4's purchase, then remove the other, including old scripts left in checkout settings.
    3. Fire on the order, not the page. Trigger the purchase tag on the real confirmation event, such as a data layer purchase push or Shopify's checkout_completed, with a condition that the transaction ID isn't empty.
    4. Block repeats in the browser. Store each transaction ID after the tag fires, in a cookie or local storage, and block the tag if the ID is already there. Simo Ahava's free Transaction ID Logger and Reader templates do this in Tag Manager. It won't catch a different device.
    5. Block repeats on the server, if you run a server container: a duplicate transaction check that remembers recent IDs catches copies from any device.
    6. Check it with a test order, then reload the confirmation page and open it on your phone. GA4 should still show one purchase.

    What you can't fix

    past duplicates stay in GA4. A data deletion request replaces text values but, in Google's words, "the event will still be counted in the overall metrics". Fix it going forward, add an annotation on the date, and remove repeats in BigQuery or your reporting layer if you need clean history.

    Quick check

    Quick check

    • No transaction ID with more than one E-commerce purchase in the last 30 days.
    • No (not set) or empty transaction IDs.
    • Every transaction ID matches an order number in your store.
    • Only one setup sends the purchase to each GA4 property.
    • The purchase tag fires on the order event, not on a page view.
    • A reload of the confirmation page doesn't add a purchase.

    Ask yourself

    If 2.5% of your GA4 revenue were orders counted twice, which report would you have trusted that you shouldn't have?

    The free GA4 Auditor checks 30 days of your purchases for repeated transaction IDs, missing IDs and purchases without a value, and shows the count and revenue of every duplicate. Add an orders export and it compares GA4's revenue with your real sales. Read-only. Check my GA4 purchases

    Frequently asked questions

    Does GA4 deduplicate transactions?

    Partly. Google says GA4 removes purchase events with the same transaction ID, on web streams only, and describes them as repeats from the same user. It doesn't publish a time window. Repeats with a different ID are counted again, and in our data repeats arriving in other sessions were too.

    Why does GA4 show more purchases than orders?

    Usually duplicates: the confirmation page loading twice, two setups sending the purchase, or a browser and a server copy with different IDs. Orders from other channels that end on your checkout can also appear. Check the Transactions report for IDs counted more than once.

    How do I remove duplicate transactions from GA4?

    You can't remove them from past data. Data deletion requests keep the events counted and don't delete numeric values. Fix the tags, annotate the date, and deduplicate history in BigQuery or your own reports.

    What is the difference between Transactions and E-commerce purchases in GA4?

    E-commerce purchases counts only the purchase event. Transactions also counts refunds and app subscription events. Use E-commerce purchases per transaction ID to spot duplicates.

    Can an empty transaction ID cause problems?

    Yes. Google says GA4 deduplicates all purchase events with an empty transaction ID, so different orders collapse into one and you undercount. If you don't have the order ID, fix the data layer rather than sending a placeholder.

    Does Shopify's thank-you page fire the purchase twice?

    The new thank-you page is a one-time page, and Shopify's checkout_completed event fires once per checkout. The order status page can be revisited, so tags that send a purchase on page views there can count again.

    Sources

    Published

    Share
    Qudees Kiani, founder of Swishiy

    Qudees Kiani

    Founder of Swishiy. Five years of marketing measurement work across Google Ads, Meta and GA4, for ecommerce and lead-gen businesses.

    Book a 30-minute call

    Is your Google Ads data telling the truth?

    The free auditor checks tracking, brand vs non-brand and wasted spend. Automated, Google Ads only, 60 seconds.

    Run the free audit

    More on GA4

    GA4

    GA4 Key Events: Which to Mark, Which to Unmark

    What a GA4 key event does and doesn't do, which events to mark for shops, lead gen, SaaS and content sites, and how a key event ends up bidding in Google Ads.

    · 8 min read