Skip to main
← Index

Connect Snapchat Conversions API

Send your conversions to Snapchat server-side with a Pixel ID + access token, with deduplication against the browser Snap Pixel.

Walityk sends your events to the Snapchat Conversions API (v3), server-side, with event_id deduplication against the browser Snap Pixel. Personal data (email, phone, user ID) is SHA-256 hashed before sending.

Takes 5 minutes.

Prerequisites

  • A Snapchat Ads account with a Snap Pixel created in the Events Manager.

1. Get the identifiers

  1. Pixel ID: Snapchat Ads Manager → Events Manager → your Snap Pixel. The ID is a UUID (format b1234567-89ab-cdef-0123-456789abcdef).
  2. Access Token: generate a token with the snapchat-marketing-api scope (Snapchat Business → Conversions API → token generation). This token authorizes server-side sending.

2. Configure the destination

  1. Walityk dashboard → Destinations → your site → Snapchat Conversions API card.
  2. Paste the Pixel ID and Access Token.
  3. Save.

3. What Walityk sends

  • Events are mapped to Snapchat’s standard event set: PAGE_VIEW, VIEW_CONTENT, ADD_CART, START_CHECKOUT, PURCHASE, SIGN_UP, SEARCH. An unrecognized custom event is sent as CUSTOM_EVENT_1.
  • User matching: email and phone (if captured) are SHA-256 hashed; the visitor ID is sent as a hashed external_id; the User-Agent is passed through.
  • The Snapchat click (ScCid) is captured automatically from landing URLs and forwarded unhashed as sc_click_id: no tag-side configuration.
  • Order value and currency, order_id, and content_ids are forwarded in custom_data.

4. Deduplication with the browser Snap Pixel

  • If you keep your Snap Pixel on the site, Walityk sends the server copy with the same event_id → Snapchat automatically deduplicates the two signals.
  • Without a browser pixel, only the server-side Conversions API runs — enough for campaign tracking (and resistant to ad blockers).

5. Verify

  1. Destinations → your site → Snapchat: delivery log.
  2. On the Snapchat side: Ads Manager → Events Manager → the history of events received via the API.

Common errors

  • HTTP 401/403: token missing the snapchat-marketing-api scope, or expired → regenerate it.
  • HTTP 400: Pixel ID copied incorrectly (check the UUID format).
  • Ad consent is respected: if the visitor denies ad_user_data, the event is not sent to Snapchat.

Next steps

Need help? hi@walityk.com.