Analytics and Tracking

Event Deduplication

Also called dedup, event ID matching

The matching of browser and server copies of the same action by a shared ID so one conversion is not counted twice.

Quick facts: Event Deduplication

Category
Analytics and Tracking
Also called
dedup, event ID matching
Level
Advanced
Affects
Reported conversions, return on ad spend, bidding accuracy
Where to see it
Meta Events Manager (event overlap and deduplication status), Google Tag Manager, server logs
In this article4
  1. How event deduplication works
  2. Why event deduplication matters
  3. Where event deduplication goes wrong
  4. How to act on it

How event deduplication works

Modern tracking sends the same action twice on purpose. The browser sends one copy through a tracking pixel such as the Meta Pixel, and your server sends a second copy through the Conversions API, so that if the browser copy is blocked — an ad blocker, browser tracking prevention, a tab closed too early — the server copy still arrives. That redundancy is the whole point, and it creates the problem it then has to solve: one purchase, two records.

Deduplication is how the platform decides those two records describe the same purchase. Both copies carry a shared identifier, normally an event ID generated once and passed into both paths, alongside the event name and its timing. When the second copy arrives and the platform recognises the pairing, it keeps one and discards the other. Meta matches on event name plus event ID; Google’s equivalents lean on transaction and order IDs in much the same spirit.

Why event deduplication matters

Without it, every sale that succeeds on both paths is counted twice. Reported revenue inflates, cost per acquisition looks better than it is, and return on ad spend flatters campaigns that have not earned it. The damage does not stop at reporting: automated bidding learns from those same inflated numbers, so budget drifts towards whatever happens to double-count most.

Getting it right is also what makes running both paths safe, which is the reason for adding a server connection in the first place. Deduplication is the condition attached to redundancy.

Where event deduplication goes wrong

The identifier is where nearly all failures live. If the browser and the server each generate their own ID, nothing matches and both copies survive. If the ID is regenerated on a page refresh, a customer who reloads the confirmation page creates fresh duplicates. If the event name differs by a single character between the two paths, the platform will not attempt the match at all.

Timing accounts for the rest. A server copy that arrives long after its browser twin can fall outside the matching window and be treated as new, and so can a queued request retried after a failed job. A confirmation page that customers can revisit or bookmark will fire again unless the site refuses to re-send an order it has already reported.

How to act on it

Generate the event ID once — on the server, or at the moment the order record is created — and pass that same value into both the browser call and the API call. Where an order or transaction number already exists, reuse it: it is naturally unique and already stored, so nothing has to be invented or kept in sync. Keep the event names identical, character for character, across both paths.

Then verify rather than assume. Events Manager reports whether events were received from both sources and whether they were deduplicated or processed separately, and a test purchase checked against your own order records will expose a gap quickly. Where a browser pixel and a server connection run together, treat deduplication as part of the pixel and Conversions API build rather than a later fix, and re-test after any change to the checkout.

Do and do not

Do

  • Generate one event ID and pass it to both paths
  • Reuse the order number as the event ID
  • Keep event names identical between browser and server

Do not

  • Let each path create its own identifier
  • Regenerate the ID when the confirmation page reloads
  • Assume deduplication works without checking platform diagnostics

Questions people ask about this

How do I know if my events are being deduplicated?

Check the platform's own diagnostics. Meta's Events Manager labels events received from both the browser and the server and shows whether they were deduplicated or processed as separate records. Alongside that, compare the conversions reported for a quiet day against your actual order list. A consistent gap upwards is the clearest sign that matching is failing.

Can I turn the pixel off and send everything from the server?

You can, but you usually lose more than you gain. The browser copy carries signals the server does not see easily, such as the browser identifier and the page context, and those help match a conversion back to the person who saw the ad. Running both paths with reliable deduplication is normally stronger than either path alone.

Does deduplication fix double counting in Google Analytics too?

Not through the same mechanism. GA4 relies on a unique transaction ID to avoid counting a purchase twice when a confirmation page is reloaded, so setting one on every order matters there as well. The principle is identical — one action, one identifier — but each platform matches on its own fields and has to be configured separately.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.