About event deduplication

Event deduplication is required if you use both the TikTok Pixel and Events API to share duplicate copies of events, which report the exact conversion on their website. If we recognize that events overlap and are duplicate copies of the exact conversion, we will keep and enrich (see below) the first event to ensure that duplicate event counts do not occur for measurement and reporting purposes. You can use deduplicated events to help measure, optimize, and target your ads on TikTok.

Features

You must share Event ID (event_id) as a parameter through both Pixel and Events API to ensure deduplication takes place. If TikTok recognizes that events overlap and duplicates of each other, we will record the first event received for measurement and reporting.

Key concepts

Deduplication is not required if you share different events separately between the Pixel and the Events API, without event overlap. For example, sharing AddToCart events through the Pixel, and Purchase events through the Events API.

Deduplication is required if you share the same events through the Pixel and the Events API, with event overlap. For example, sharing Purchase events through both Pixel and the Events API.

Examples

There are three overlapping scenarios that can occur with events:

• Overlapping between Pixel events: We deduplicate any events shared through Pixel, with the identical event and event_id parameters arriving within a 48-hour window from the first event.

• Overlap between Events API events: We deduplicate any events shared through the Events API, with the identical event and event_id parameters arriving within a 48-hour window from the first event.

• Overlap between Pixel and Events API events: We merge or deduplicate events shared by the Pixel and Events API with the identical event and event_id parameters arriving after 5 minutes and within a 48-hour window from the first event (if applicable).

Learn more about developer documentation for event deduplication.