Free check

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.

Request a tracking fix

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

How to check

  1. 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.
  2. Place a test order and count requests. DevTools, Network, "Preserve log", filter on collect. Count en=purchase requests per GA4 ID. Note which frame or script sent each one.
  3. 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.
  4. Reload the confirmation page. Note whether another purchase is sent.
  5. 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

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

  1. Pick one source per destination for the purchase. Write it down.
  2. Turn off purchase sending in the other source rather than removing it entirely, if it also does useful work.
  3. Fire the purchase on one trigger only, normally a dedicated dataLayer event.
  4. Send a stable, non-empty transaction_id in one format, and guard against reloads.
  5. In Google Ads, keep one purchase action as primary and set the other to secondary, or remove it.
  6. Filter test orders: a test discount code or internal traffic rule, applied consistently.
  7. Validate with a fresh test order and a week of per-ID counts.

What not to do

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:

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.

Request a tracking fix

Sources and updated date

Last checked against official documentation: 18 November 2026.