<b>Counting one sale twice: the deduplication detail</b>

<b>Counting one sale twice: the deduplication detail</b>

Earlier we said pros run both a Pixel (browser) and the Events API (server). Now the natural worry: if both report the same purchase, won't TikTok count it twice and ruin your numbers?

Great instinct, and TikTok solved it with deduplication, meaning it spots when two reports are actually the same sale and counts it once.

The trick is giving each event a matching 'Event ID' from both sources:

— Pixel sends a purchase with ID 'abc123'
— Events API sends the same purchase with ID 'abc123'
— TikTok sees the matching ID and merges them into one

Without matching IDs, your sales numbers inflate and you'll trust bad data.

Don't worry if this is the most technical post yet, you only set it up once.

Try this: if you run dual tracking, ask whoever set it up: 'are we sending matching Event IDs?' That one question protects all your data.