Free check

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.

Check my ad conversions

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

  1. Browser and server events without matching IDs. Meta's deduplication guide says the pixel's eventID must match the Conversions API event_id, and the event names must match.
  2. 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.
  3. Two server integrations. A platform app and a separate server-side setup both send server Purchase events.
  4. The confirmation page fires again. A customer reloads or returns to the order status page and the purchase event fires a second time.
  5. Different event names. One source sends Purchase and another a custom name such as purchase_complete. They are counted as different events and never merged.

How to check

  1. Pick one real or test order. Note the order number, time and value. You will follow this one order through every tool.
  2. Look at the browser side. On the confirmation page, filter the Network tab for facebook.com/tr and find requests with ev=Purchase. Count them, note each id= (pixel ID) and the eid= value if present. That is the browser event ID.
  3. 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_id sent.
  4. Compare. Same event name? Same event ID string, character for character? Sent to the same pixel or dataset ID?
  5. 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.
  6. 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

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

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

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

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.

Get a free check