Duplicate Purchase Events in Shopify: Why They Happen and How to Diagnose Them

What a duplicate purchase event looks like

A single real order shows up as two or more purchase events in your reporting. Your Shopify orders show 100 purchases but GA4 shows 180 and Meta shows 190. The extra counts are not real customers. They are the same order being sent more than once.

The danger is that bidding algorithms trust these numbers. Double counted purchases make cost per acquisition look half of what it really is, which leads to overspending on the wrong traffic.

Why duplicates happen

Most duplicates come from one of three causes: multiple tracking implementations firing on the same order, a thank you page reload re-firing the event, or a missing transaction ID so the platforms cannot recognize the repeat. Diagnosing which one is happening tells you where to fix it.

Multiple tracking implementations

The most common cause is having more than one tag for the same platform. A Shopify native Meta integration and a GTM Meta tag both firing on the thank you page sends the purchase twice. The same happens with Google Ads tags installed both through an app and through GTM.

The fix is to choose one implementation per platform and remove the other. Two paths do not mean more accurate data, they mean double counting.

Shopify integrations and GTM

Shopify has native integrations for Google and Meta that are easy to enable. If you also run GTM on top, you can easily end up with both firing. Decide which one you want as your tracking layer and disable the other. Document the choice so it does not get re-enabled later by mistake.

GA4, Google Ads and Meta Pixel

Each platform can have its own duplicate source. GA4 duplicates often come from a purchase event firing on thank you page load without a transaction ID check. Google Ads duplicates come from two conversion tags. Meta duplicates come from Pixel and CAPI without event ID deduplication. Diagnose each platform separately.

Event ID and transaction ID

The transaction ID from Shopify is the key to deduplication across GA4, Google Ads and Meta. When every platform receives the same transaction ID, each can recognize a repeat and count the order once. Without it, the platforms have no way to know they are seeing the same purchase.

For Meta specifically, the event ID lets the Pixel and CAPI deduplicate against each other. Both send the same event ID for the same order and Meta counts it once.

Deduplication

Deduplication only works when the identifiers match exactly. A transaction ID sent as a string in one place and a number in another will not match. Confirm the format is consistent across every tag and integration that sends the purchase event.

Thank you page tracking

The thank you page is where most purchase events fire, and it is also where most reloads happen. A customer who refreshes the thank you page or navigates back to it can re-trigger the event. Fire the purchase on a real order completion using the data layer or a server event, and use the transaction ID to prevent reloads from counting twice.

How to diagnose before changing anything

Do not start deleting tags. First find out which tag is firing twice. Open your debugging tools, place a real test order, and watch what fires on the thank you page. Count how many times each platform receives the purchase event and from which source. Only when you know the source should you change anything.

1. 1.Place a real test order with a small value.
2. 2.Open GA4 debug mode, Google Ads Tag Assistant and Meta Events Manager.
3. 3.Count how many purchase events each platform receives.
4. 4.Identify which tag or integration sent each one.
5. 5.Remove or fix only the source causing the duplicate.

Testing after the fix

After making a change, place another test order and confirm each platform now receives exactly one purchase event with the correct value and transaction ID. If the count is still wrong, you removed the wrong source or the deduplication is not working. Keep testing until one order equals one event everywhere.

Debugging ongoing

Duplicates can return after a theme update, an app install or a platform change. Compare your platform purchase counts to your Shopify order count regularly. If they drift apart again, a new duplicate source has appeared.