Deduplication

Deduplication is a critical process in the Conversion API to ensure accurate tracking and attribution of events. This documentation outlines the deduplication rules for Conversion API events based on their arrival times and the use of event_id and event_name for deduplication.

Deduplication of Conversion API Events

Conversion API events are deduplicated when multiple events arrive within a specific time window of each other. The deduplication process ensures that only one of the events is considered for tracking and attribution, preventing duplicate data and inaccuracies.

Deduplication Rules:

1. If two Conversion API events with the same event_id and event_name arrive within 60 seconds of each other, the event that arrives first is discarded, and only the second event is considered for tracking and attribution.

Example Scenario:

Suppose two Conversion API events with the same event_id and event_name arrive as follows:

Event A: event_id = "abcd1234", event_name = "purchase", event_time = 1677649421  
Event B: event_id = "abcd1234", event_name = "purchase", event_time = 1677649485

In this case, Event A arrives at timestamp 1677649421, and Event B arrives at timestamp 1677649485. Since these events have the same event_id and event_name and arrive within 60 seconds of each other, Event A (the first event) will be discarded, and only Event B will be considered for tracking and attribution.

Deduplication of Conversion API Events and Pixel Events

In some cases, both Conversion API events and Pixel events might be used for tracking. To ensure accurate deduplication across these event types, the deduplication process considers events that arrive within a specified time window of each other.

Deduplication Rules:

1. If a Conversion API event and a Pixel event share the same event_id and event_name and arrive within 48 hours of each other, the Pixel event takes precedence over the Conversion API event. The Conversion API event is discarded, and only the Pixel event is considered for tracking and attribution.

Example Scenario:

Consider the following events:

Conversion API Event: event_id = "efgh5678", event_name = "signup", event_time = 1677854321

Pixel Event: event_id = "efgh5678", event_name = "signup", event_time = 1677857800

In this case, the Conversion API event arrives at timestamp 1677854321 , and the Pixel event arrives at timestamp 1677857800 . Since these events have the same event_id and event_name and arrive within 48 hours of each other, the Conversion API event will be discarded, and only the Pixel API event will be considered for tracking and attribution.