Meta Purchase Event Firing Twice: How to Find the Duplicate

Meta and CAPI · 4 min read · by Anna Viggeborn

If Meta reports roughly twice the purchases your store recorded, you rarely have a reporting bug. You have two sources sending the same event, or one source sending it twice.

The usual suspects

The pixel is installed both in the theme and through a tag manager.
Browser and server events without matching event_id.
A confirmation page that reloads or is reachable again from history.
A tag manager trigger that fires on both page view and a custom event.
A platform app and a manual snippet doing the same job.

How to isolate it

1. Complete one test order

2. Test Events: how many Purchase events for that single order?

3. Note the source of each: browser or server

4. If both browser: look for two pixel installs

5. If browser plus server: check event_id on both

What it means for decisions

Double counting inflates ROAS, which means budget gets pushed toward campaigns that look stronger than they are. It is the most expensive quiet failure in paid social.

Not sure whether you have a performance problem or a signal problem?

Your performance may be fine. Your signals aren't.

Run a free Milestic Signal Audit

Continue the diagnostic path

Meta CAPI deduplication

Two paths for the same purchase. How Meta decides they are one event.

GTM duplicate events

One action, two events. The trigger patterns that cause it.

GA4 revenue not matching Shopify

Some difference is normal. Learn which size of gap is a real problem.