Meta Pixel and Conversions API: how deduplication works

Meta deduplicates a purchase sent from the Pixel and from the Conversions API when both copies carry the same event_id and the same event name, and the second one arrives within 48 hours of the first. Get that ID right and Meta counts the order once. Get it wrong and Meta counts each such order twice. Our guide to server-side tracking for online shops has the bigger picture.

Sending both copies is the point. The Pixel catches the shopper’s browser context (the ad click, the _fbp cookie), and the server copy arrives even when the browser request is blocked or the thank-you page never loads. Meta keeps one.

How Meta matches the two copies

Meta looks at three things:

  • The event name. Purchase from the Pixel matches Purchase from the server, not purchase or a custom name.
  • The event_id. Both copies must carry exactly the same string.
  • Time. The second copy has to arrive within 48 hours of the first one Meta received with that ID.

Where the ID comes from is up to you. It must be something both the browser and the server know before either sends: the order. A hash of your shop’s ID and the order ID works, because the thank-you page and the backend both have the order ID. A random value generated in the browser doesn’t, because the server never sees it.

Setups that still count the order twice

Two server copies

Meta deduplicates the Pixel against the server. It does not deduplicate two events that both come from a server. If two integrations send the purchase through the Conversions API, Meta counts both, even with the same event_id.

In WooCommerce this happens when the official Facebook for WooCommerce plugin, or another tracking plugin, sends its own Conversions API purchase with its own event_id, next to the one you set up. Turn off purchase events in all but one of them.

A different ID in the browser and on the server

The Pixel fires on the thank-you page with one ID; the backend sends with another, for example the order number in one place and the internal order ID in the other. Meta sees two unrelated purchases.

A renamed event

The browser sends Purchase, a server integration sends a custom event such as OrderPaid. Same order, two event names, no deduplication.

The second copy arrives late

A bank transfer confirmed three days later, sent from the server only then, falls outside the 48-hour window after the Pixel’s purchase. Rare, but it happens with slow payment methods.

How to check it

  1. Place a test order with full consent.
  2. In Meta Events Manager, use Test Events with your test code and check that the purchase shows once, received from both the browser and the server. Test Events only shows what arrives: Meta still counts those events in reporting and targeting, so keep test orders few or use a pixel you don’t advertise with.
  3. Place a second test order with ad cookies rejected. Without ad consent, nothing should reach Meta from either side.
  4. If the first order shows up twice, look for a second integration sending Conversions API purchases.

The other platforms do it differently

Matching rules differ by platform, and a setup that is right for Meta can still count twice somewhere else.

Platform Matches the browser and server copies by Notes
Meta event_id + event name, within 48 hours Two server copies are not deduplicated
TikTok pixel + event name + event_id, within 48 hours Also deduplicates two server copies; copies within 5 minutes are merged
GA4 transaction_id of the purchase The event ID plays no part
Google Ads transactionId of the conversion A refund with the same ID changes the value, not the count

So the transaction ID you send to GA4 and Google Ads has to be identical in the browser tag and in the server copy, and that is a different field from the event_id Meta and TikTok use. Our article on why GA4 shows fewer orders than WooCommerce covers the GA4 side.

How TallyHost handles it

TallyHost builds the same event_id for the browser and the server copy from your site and the order. When your shop reports purchases from the server, a browser purchase waits up to 15 minutes for the server copy, and the server copy wins if it arrives in that time. If it arrives later (a transfer paid days after the order), both copies go out through the Conversions API, and Meta counts that order twice, because it doesn’t merge two server copies. TikTok keeps the first one. Each delivery and the platform’s answer are in the debugger, so a double count shows up there before it shows up in your ROAS. The features page explains how purchases from the server work.

Send your shop's orders from the server

TallyHost reports paid orders with consent checked, to Meta, TikTok, GA4 and Google Ads. Free up to 100,000 events a month.

Start free

Read next