Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Deduplication

Removing double counts when one conversion is reported by more than one source.
AnalyticsprocessUpdated

Definition

Deduplication removes duplicate records of one action so that totals reflect what happened. In conversion tracking the term covers two kinds of double counting that look alike in a report:

  • Duplicate events within one platform. The same action reaches a platform by two routes, typically a browser tag and a server connection, or a tag that fires again when a confirmation page is refreshed. The platform sees two events unless something marks them as one.
  • Duplicate claims across partners and channels. Several systems each credit themselves with the same order under their own rules and windows. Nothing is technically duplicated inside any one of them; the duplication appears only when their totals are added together, or when each is paid.

The distinction matters because the fixes do not overlap. An event identifier cannot settle which affiliate deserves a commission, and a commission rule cannot stop a platform counting a purchase twice.

In practice: browser and server events

Running a browser pixel and a server-side connection together is the recommended setup on the major social platforms, because the server recovers events that blockers, consent choices and browser limits remove. It also creates the duplicate problem. Meta documents the event ID and the event name as the main keys: when a browser event and a server event carry the same ID and name and arrive within its deduplication window, they are counted once. The Conversions API guide sets out the requirements: one ID generated per action, the same event name on both routes, both copies carrying the ID, the server copy sent promptly and retries reusing the original ID. TikTok's Events API follows the same pattern, as the TikTok pixel and Events API tutorial shows.

The most reliable source for the identifier is the record that represents the action, such as the order number or the lead's record ID, passed to the browser through the data layer and read by the server from the same record.

Cross-partner deduplication and commission rules

In affiliate programmes the duplication is commercial. The affiliate platform credits the last affiliate click within its cookie window, the search platform credits its own click within its window, and email credits its open, so one order can appear in three reports and, without a rule, be paid as a commission while also justifying search spend. The affiliate attribution and deduplication guide describes the two usual mechanisms: the site decides at the moment of conversion whether to fire the affiliate postback, based on the last marketing touch it recorded, or the advertiser rejects conversions another channel should win when it validates pending commissions. The rule has to be in the programme terms before disputes arise, as the affiliate sales playbook stresses, and it is one part of the wider affiliate measurement picture alongside reconciliation and incrementality.

How to check that deduplication works

  • Compare with the source of truth. Platform purchases or leads should sit close to the back-office count for the same period; a ratio well above one means duplicates are getting through.
  • Read the platform's diagnostics. Events Manager shows, per event, how many arrived by each route and how many were deduplicated; a share near zero after launch means IDs or names do not match.
  • Test one known action. Place a test order and confirm both copies arrive with the same ID and are marked as merged.
  • Audit it as a gate. The Meta Ads account audit scores server events with working deduplication before it scores anything that depends on the conversion signal.
Illustrative example — not a real result

Bookings that doubled overnight

Ironbark Tool Hire adds server-side events to its Meta setup on a Monday. By Friday the ad account reports 212 bookings for the week against 118 in the booking system, and the platform's cost per booking has nearly halved. Events Manager shows browser and server events both arriving, with a deduplicated share close to zero: the pixel sends its own random ID while the server sends the booking reference. The developer changes the pixel to read the booking reference from the data layer. The following week the account reports 131 bookings against 124 in the system, the gap now coming from people who booked by phone after clicking, and the bid strategy is left to relearn on the corrected figures before any budget changes.

The Conversions API is the server route that creates the need for event-level deduplication. Attribution decides how credit is shared across touches; deduplication decides that one action is counted, or paid, only once. Each platform's Lookback Window sets how far back it reaches to claim a conversion, so overlapping windows are what make cross-channel claims collide. Consistent UTM tagging lets analytics and the order system see which channel a session came from, which is the evidence a cross-channel deduplication rule relies on.

Common confusions

  • Deduplication is not attribution. Attribution shares credit; deduplication stops one action being counted twice.
  • A shared event name is not enough. Without a matching ID, two copies of a purchase stay two purchases.
  • Platform totals are not meant to add up. Summing each channel's claims double-counts by design.
  • A sudden fall in cost per conversion after a tracking change is not good news until duplicates are ruled out.
  • Fixing the tag does not fix the past. Reports and bid strategies trained on doubled data need time to settle.

More terms to look up

Where this term is used

Sources

  1. About the Conversions API — Meta Business Help Centre

Related