Meta reporting duplicate purchases?
The usual cause is the same purchase reaching Meta twice without a shared event ID: once from the browser pixel and once from the Conversions API, or from two separate pixel installs. Meta can only merge them when the event name and event ID match.
Symptom
Events Manager shows more Purchase events than your store has orders, or one test order appears twice. Purchase value in Meta looks roughly double what you took.
The direct answer: compare one known order end to end. If it arrives from two sources with different event IDs, or with no event ID, deduplication can't work. Fix the ID, or remove one of the sources.
Possible causes
- Browser and server events without matching IDs. Meta's deduplication guide says the pixel's
eventIDmust match the Conversions APIevent_id, and the event names must match. - Two browser installs. The pixel is in the theme and also added by the Facebook & Instagram app, or by a tag manager. Each sends its own Purchase.
- Two server integrations. A platform app and a separate server-side setup both send server Purchase events.
- The confirmation page fires again. A customer reloads or returns to the order status page and the purchase event fires a second time.
- Different event names. One source sends
Purchaseand another a custom name such aspurchase_complete. They are counted as different events and never merged.
How to check
- Pick one real or test order. Note the order number, time and value. You will follow this one order through every tool.
- Look at the browser side. On the confirmation page, filter the Network tab for
facebook.com/trand find requests withev=Purchase. Count them, note eachid=(pixel ID) and theeid=value if present. That is the browser event ID. - Look at the server side. In Events Manager, open the dataset and use Test events, or check your server logs or integration logs, for the same order. Note the
event_idsent. - Compare. Same event name? Same event ID string, character for character? Sent to the same pixel or dataset ID?
- Read Events Manager's own view. On the dataset overview, open the Purchase event and check how it reports browser and server sources and deduplication. Wording varies, so look for what it says about events received from both sources.
- Count installs. On Shopify, list app pixels and custom pixels under Settings, then Customer events, and search the theme for
fbq('init'. Elsewhere, check the theme, the tag manager and plugins.
Illustrative example of a mismatch, with invented values:
| Source | Event name | Event ID |
|---|---|---|
| Browser pixel | Purchase |
order_1001 |
| Conversions API | Purchase |
1001 |
These two will not deduplicate. Both IDs must be the same string, for example 1001 in both.
What the result means
- Two browser requests with different pixel IDs: two pixels, so events are split rather than duplicated in one dataset. Decide which pixel is the real one.
- Two browser requests to the same pixel: a duplicate install. Remove one.
- Browser and server with no or different IDs: deduplication can't work. Fix the ID mapping.
- IDs match but counts still look high: check timing. Meta's guide says event ID deduplication only applies when the events arrive within 48 hours of each other.
A limitation to keep in mind: more purchases in Ads Manager than orders in your store is not proof of duplication. Ads Manager reports conversions attributed to ads under your attribution setting, and can count view-through conversions. Always prove a duplicate with one order traced through both sources.
How to fix it
- Use one browser install and, if you need it, one server integration for each dataset.
- Generate one event ID per order, from a stable value such as the order ID, and send it from both sides. On the pixel it goes in the fourth argument, for example
fbq('track', 'Purchase', {...}, {eventID: '1001'}). - Send the same event name from both sides, using Meta's standard
Purchase. - Stop the confirmation page firing twice for the same order, for example by recording that the order has already been sent.
- Meta also describes a fallback using
fbporexternal_id, but its guide says that method only works when the browser event arrives first. Prefer event IDs.
On Shopify, if the Facebook & Instagram app sends both browser and server events, adding your own custom pixel or server integration for the same dataset is a common way to create duplicates. Change one source at a time and retest.
What not to do
- Don't delete the server integration just because numbers rose. You may lose events that browsers block.
- Don't "fix" counts by changing the attribution setting. That changes reporting, not data quality.
- Don't generate a random event ID on each side. Random IDs never match.
When to request help
If you can't trace one order cleanly through both paths, our Google Ads and Meta conversions service maps every source, event name and ID and validates the result with a test order. If the duplicates also show in Google Analytics 4 (GA4), see our conversion tracking fix.
Related guides: Meta Conversions API not receiving events, Meta Pixel not firing, duplicate purchase events in GA4 and the Shopify tracking checklist.
Sources and updated date
- Meta for Developers: Handling duplicate Pixel and Conversions API events
- Meta for Developers: Server event parameters
- Meta for Developers: Meta Pixel reference
Last checked against official documentation: 18 November 2026. Events Manager screens change often, so if a label differs from what you see, follow Meta's current help.
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.