Deduplication
How it works
Duplicate conversions come from two places, and each needs its own fix:
- Between pixel and server: when browser and server report the same event, the platform recognizes the pair by a shared event ID (in Meta's case together with the event name) and keeps only one report.
- In your own measurement: the thank-you page gets reloaded, the form is submitted in a second tab, or a webhook arrives twice. A rule that counts the same event of the same person, or the same order number, only once takes care of this.
Why it matters
Duplicate conversions distort everything built on top of them. CPL seems to drop, ROAS seems to rise, and the bidding algorithm puts budget into ads that deliver less than it looks. Now that pixel and Conversion API usually run side by side, deduplication is a must.
TSO gives pixel and server the same event ID and suppresses duplicates from reloads, second tabs or a repeated order ID.
Example
An online store has 300 orders a month. Pixel and Conversions API both report every order to Meta. The pixel gets through for 240 orders, the server for all 300.
- Without a shared event ID: Meta counts 240 + 300 = 540 purchases
- With a shared event ID: Meta recognizes 240 pairs and counts 300 purchases
On top of that, 15 customers open their order confirmation again later. Without a rule for the order number, each of those visits counts as a new purchase.
Common mistakes
- IDs created separately: browser and server each generate their own random ID. To the platform these are two different events.
- Event names don't match: in Meta, the name has to match as well as the ID. If the pixel sends
Purchaseand the server a custom event calledOrder, nothing gets merged. - Old pixel without an ID: a forgotten, hard-coded pixel keeps reporting the same events, but without an event ID. The server events find no partner and count on top.
- Expecting deduplication across platforms: each platform only deduplicates its own events. When Meta and Google both claim the same purchase, only your own attribution sorts that out.