wesaw
FRGet started

Event deduplication

Also known as: deduplication, event_id matching, double counting

Event deduplication is how an ad platform recognises that two reports of the same sale, one from the shopper's browser and one from the shop's server, are the same event and must be counted once. The platform matches them on a shared identifier the shop sends with both.

Why would the same sale be reported twice?

Because most shops run both a pixel and a server connection on purpose. The pixel reports what the browser saw; the server reports what the shop recorded. Sending both is what recovers the sales the browser loses, and event deduplication is the mechanism that stops the overlap becoming double counting.

For the browser/server pair, check both the event name and event identifier, along with destination diagnostics. Two recorded emissions alone do not establish that Meta merged them.

What makes event deduplication fail?

Mismatched event names or identifiers can prevent Meta from recognising the intended pair. Check the exact identifier and its capitalisation on both paths, and look for independent purchase senders. A difference is evidence to investigate, not a measured count of duplicate attributed purchases.

What does a broken deduplication cost?

Inflated numbers you then optimise against. A campaign credited with twice the sales it produced looks twice as profitable, so budget moves toward it and away from campaigns reporting honestly. The reporting error becomes a spending error, which is the expensive half.

Sources

  • Meta deduplicates browser and server events that share the same `event_name` and `event_id`, and treats the identifier as case-sensitive.Meta for Developers
  • wesaw derives its purchase event identifier from the order ID and applies pipeline idempotence. This does not expose Meta's final merge or attribution decision.wesaw, own test store

Last reviewed: