Configure Events Deduplication in Snapchat

Snapchat Event Deduplication merges conversions that share the same event_id, even when they're tracked by both the Snap Pixel (client-side) and the Conversions API (server-side). By counting only one conversion, it ensures your reports stay accurate.
Follow this step-by-step guide to set up Snapchat Event Deduplication.

Create a unique Event ID

Use a custom JavaScript variable in GTM:

function() {
  return 'snap_evt_' + Date.now() + '_' + Math.floor(Math.random() * 100000);
}

Push the Event ID to the data layer

On the relevant event (e.g., purchase, add_to_cart), push the event_id along with other event data:

window.dataLayer.push({
  event: 'purchase',
  event_id: 'tt_evt_1721456789123_45678',
  // ...other parameters
});

Reference the Event ID in GTM (web + server)

In GTM web container (Snap Pixel): Add event_id as a parameter.
In sGTM server container (CAPI): Add event_id to your HTTP request payload.

Test event deduplication

Use GTM Preview mode and Snapchat Events Manager, in Ads Manager, to ensure deduplication is working and only one conversion is counted per user action.

Best practices

Always generate and assign the event_id at the moment of the user action.
Use the exact parameter name event_id in both implementations, client- and server-side.
Ensure uniqueness to avoid accidental deduplication of separate actions.

Useful resources

Snapchat server-side tracking - The full manual

Find expert support

TABLE OF CONTENTS

Create a unique Event ID Push the Event ID to the data layer Reference the Event ID in GTM Test deduplication Best practices Useful resources