Why are purchase events counted twice?
Purchases are usually counted twice because two things send them: an app and GTM, two plugins, or a tag that fires on two triggers. Reloads, test orders and missing transaction IDs make it worse. Count purchase events per transaction ID in GA4, then trace each copy back to its source.
Symptom
GA4 or Google Ads shows more purchases than the store took. Conversion rate looks too good. Google Ads reports a cost per acquisition that would be wonderful if it were true. Or the totals look normal, but some transaction IDs appear twice in GA4.
Possible causes
- Cause A: two sources. On Shopify, the Google and YouTube app and a custom pixel or GTM both send
purchaseto the same GA4 ID. On WooCommerce, an analytics plugin and a GTM plugin both do. - Cause B: one tag, two triggers. In GTM, the GA4 purchase tag fires on a
purchasedataLayer event and also on a page view of the thank-you page. - Cause C: reloads and revisits. The thank-you page re-sends the purchase when the customer reloads it or comes back to it later, and nothing guards against it.
- Cause D: weak transaction IDs. No
transaction_id, a different format from each source, or an empty value. Google's help notes that GA4 deduplicates purchases sharing a transaction ID, and that an empty string as the ID causes all those purchases to be deduplicated together. - Cause E: ad conversions counted from two places. In Google Ads, a purchase conversion from the Google Ads tag and an imported GA4 purchase are both set as primary, so each sale counts twice in the Conversions column.
- Cause F: test orders. Staff and agency test orders reach production properties.
How to check
- Count per transaction ID. In GA4, build an Exploration with the Transaction ID dimension and the Event count metric, filtered to event name
purchase. Any ID with a count above 1 arrived more than once. - Place a test order and count requests. DevTools, Network, "Preserve log", filter on
collect. Counten=purchaserequests per GA4 ID. Note which frame or script sent each one. - Use GTM Preview where it reaches. On WooCommerce, GTM Preview shows if the purchase tag fired on two events. On Shopify checkout, use the network log, because Preview may not connect to a sandboxed pixel.
- Reload the confirmation page. Note whether another purchase is sent.
- Check Google Ads goals. In Goals, Conversions, list every purchase conversion action, its source (website tag or GA4 import) and whether it is primary or secondary.
Illustrative GA4 Exploration output, with invented IDs:
| Transaction ID | Event count | Likely reading |
|---|---|---|
| 1001 | 1 | Normal |
| 1002 | 2 | Sent twice: two sources or a reload |
| #1003 and 1003 | 1 each | Same order, two ID formats: two sources |
| (not set) | 14 | Purchases sent with no ID |
What the result means
- Two requests per test order to the same ID: cause A or B.
- Two ID formats for one order: cause A. One source uses the order name and the other the order number.
- Repeat only after reload: cause C.
- GA4 looks right but Google Ads doubles: cause E. The tracking may be fine. The account settings aren't.
False positive. Duplicate tag installation does not always mean duplicate purchases. A store can load the same GA4 ID twice while only one copy sends the purchase. And an Event count of 2 doesn't always mean your reports show 2 purchases: GA4 deduplicates purchases sharing a transaction ID, according to Google's help. Google Ads, Meta and other tools have their own rules, so check each destination separately.
From our public research. On 14 November 2026, 92 of the 975 Shopify stores we checked loaded the same GA4 ID twice. That is a screening observation: a public-page check can't confirm whether purchases are actually counted twice, or whether purchase tracking works at all.
How to fix it
- Pick one source per destination for the purchase. Write it down.
- Turn off purchase sending in the other source rather than removing it entirely, if it also does useful work.
- Fire the purchase on one trigger only, normally a dedicated dataLayer event.
- Send a stable, non-empty
transaction_idin one format, and guard against reloads. - In Google Ads, keep one purchase action as primary and set the other to secondary, or remove it.
- Filter test orders: a test discount code or internal traffic rule, applied consistently.
- Validate with a fresh test order and a week of per-ID counts.
What not to do
- Don't rely on GA4's deduplication to tidy up a double install. Your ad platforms may still count both.
- Don't switch both Google Ads purchase actions to secondary. Bidding then has no purchase goal.
- Don't delete historic data to remove duplicates. Annotate the date of the fix instead.
When to request help
A conversion tracking fix defines the duplicate, removes the extra source within an agreed scope, and validates the result with a test order and evidence.
Related guides:
- Why is the same GA4 tag loading twice?
- Google Ads conversions not recording?
- Why doesn't GA4 revenue match your store?
Not sure what's wrong?
Send us your store address. Mikael will look at the public pages and tell you what he can see, and what he can't.
Sources and updated date
- Google Analytics Help: Minimize duplicate key events with transaction IDs
- Google for Developers: Measure ecommerce
- Google Ads Help: About "All conversions"
- Shopify Developer docs: checkout_completed
- Google Tag Manager Help: Preview and debug containers
Last checked against official documentation: 18 November 2026.