To prevent event duplication, we attach a unique de-duplication ID to every event sent to Meta's servers. This ID ensures that if an event happens multiple times, Meta recognizes it as the same event and does not count it twice.
Using de-duplication IDs is a common and recommended practice in event tracking to ensure that data is accurate and without redundancy.
We ensure this is achieved, by including a unique de-duplication ID with each event sent to Facebook’s Conversion API (CAPI). You may notice more events in Facebook's Event Manager when the Meta integration is enabled, but these are guaranteed to be de-duplicated.
How We Prevent Duplicate Events
To prevent duplication, we attach a unique de-duplication ID to every event sent to Meta's servers. This ID ensures that if an event happens multiple times, Meta recognizes it as the same event and does not count it twice.
-
De-duplication ID: Each event sent from our platform to Meta includes a de-duplication ID. This ID ensures that duplicate events are prevented by linking events with the same ID together. If an event with the same de-duplication ID is received by Meta again, Meta recognizes it as the same event and prevents any duplication.
-
Event Enrichment: By using de-duplication IDs, we can send enriched event data to Meta. This allows Facebook to match and process events with the most complete or relevant data, without causing duplicates.
-
Consistency with Facebook Pixel: We make sure to use the same de-duplication ID that Facebook Pixel generates for events. This ensures that no duplicate events are sent, regardless of whether the event is triggered by the Pixel or the Conversion API.
De-duplication ensures that Meta receives accurate, enriched data, preventing inflated event counts.As a result, you'll be able to achieve more reliable reporting and enhanced optimisation for your campaigns.