Tracking

Event Deduplication

In short

Event deduplication makes sure a conversion sent through both the pixel and the Conversion API is only counted once by the ad platform.

Also known as: deduplication of events, event dedup

Event deduplication is the process an ad platform uses to recognize events that arrive twice and count them only once. You need it as soon as you report a conversion through two channels – typically through a tracking pixel in the browser and additionally through a Conversion API from your server.

How deduplication works

Both channels send a shared, unique ID for the same action. On Meta it's called event_id; on Google Ads, a transaction or order ID plays that role. The platform checks:

same event name + same event_id = same event → count once

If the ID is missing or differs between the two channels, the platform treats the events as two separate conversions.

Example

A real estate agency tracks leads with the Meta Pixel and the Conversion API. It gets 200 real leads per month.

  • Without deduplication: Meta counts up to 400 leads. With a $6,000 budget, the cost per lead looks like $15 instead of $30.
  • With deduplication: Both events carry the same event_id, Meta counts 200 leads and shows the correct $30.

Event deduplication in lead generation

Double-counted leads don't just distort your reporting. The algorithm optimizes on reported conversions – if half of them are duplicates, it gets a skewed picture of which audiences and ads actually work.

The LeadMetrics Conversion API includes an event_id for deduplication with every event. For each lead you also get a log of which events were sent to which platform. Learn more about how pixel and server work together in Client-Side vs. Server-Side Tracking.

Event deduplication vs. lead deduplication

Event deduplication happens on the ad platform's side and applies to reported events. Lead deduplication in your CRM merges duplicate contacts, for example when someone signs up twice. Both are useful, but they solve different problems.

Common mistakes

  • Different IDs: The pixel generates one ID, the server another – deduplication never kicks in.
  • Different event names: ‘Lead’ in the pixel and ‘lead_submitted’ on the server aren't recognized as the same event.
  • Never checked: Meta Events Manager shows whether events are being deduplicated. A quick look after setup saves a lot of trouble.

Ready for better tracking?

Try LeadMetrics free for 10 days and see which campaigns actually drive revenue.
Start a 10 day trial

Frequently asked questions

If you send the same event through both the browser pixel and the server-side Conversion API, the platform sees it twice. Without deduplication, conversions are double counted, your cost per lead looks too low and the algorithm optimizes on wrong numbers.

Related terms

All terms

Conversion API · CAPI

A Conversion API (CAPI) is an interface that sends conversions directly from server to server to ad platforms like Meta or Google, without the browser.

Tracking Pixel

A tracking pixel is a snippet of code from an ad platform that captures page views and conversions in the browser and reports them to Meta, Google and others.

Server-Side Tracking

Server-side tracking sends tracking data to ad and analytics platforms from a server instead of the browser – more robust and under your control.

Event Match Quality

Event Match Quality (EMQ) is a Meta score from 0 to 10 that rates how well your server events can be matched to a Meta account using customer data.

Conversion Tracking

Conversion tracking records which users complete a desired action after clicking an ad – such as submitting a form, booking a call or buying.

Client-Side Tracking

Client-side tracking captures user actions with JavaScript directly in the browser and sends them from there to analytics and ad platforms.