> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming/destinations/advertising/snap/snap-conversions-api.md). # Snap Conversions API The **Snapchat Conversions API** (CAPI) is a server-side integration that sends event data directly from Chord to Snapchat's servers. Unlike the [Snap Pixel](/activate/event-streaming/destinations/advertising/snap/snap-pixel.md), which runs in the browser, the Conversions API sends events from the server, so ad blockers and browser tracking restrictions don't affect them. Snapchat recommends using the Conversions API alongside the Snap Pixel for maximum data coverage. When both are configured, Snapchat automatically deduplicates events using the `client_dedup_id` field, which Chord sets to the event's `messageId` on both sides. See [Snap](/activate/event-streaming/destinations/advertising/snap.md) for how the two fit together. ## Getting started You need: * Your Snapchat Pixel ID, found in Snapchat Ads Manager under **Events Manager > Pixel Details**. * A Conversions API token, found in Snapchat Ads Manager under **Business Details**. ## Settings * **Destination Name** (required): a name to tell this destination apart. * **Pixel ID** (required): the Pixel ID for your Snapchat ad account. * **Access Token** (required): your Conversions API token. * **Test Mode** (optional): sends events to Snapchat's `/validate` endpoint, so they appear in the Snapchat debug tool without affecting live reporting. Off by default. * **Product Content ID Field** (required): which product field to send as `item_id`: `variant_id`, `sku` or `product_id`. Defaults to `sku`. It must match the Item ID in your Snap catalog, and it must be the same on the Snap Pixel destination. For Shopify stores that use the native catalog sync, use `variant_id`. If the chosen field is missing on a product, Chord falls back through `sku`, `variant_id`, `product_id` and `id`. * **Consent Requirements** (optional): the consent categories a visitor must accept before Chord sends data to this destination. See [Consent](/activate/event-streaming/consent.md). ## Connect Add **Snapchat Conversions API** from the destination catalog, using the settings above. See [Connect a destination](/activate/event-streaming/connect-a-destination.md) for the full steps. ## Event mapping | Chord event | Snap event | Notes | | --------------------------------------------------------------------------------------- | ----------------- | ----- | | `page` | `PAGE_VIEW` | | | [`Order Completed`](/collect-data/tracking-plan/order-completed.md) | `PURCHASE` | | | [`Product Added`](/collect-data/tracking-plan/product-added.md) | `ADD_CART` | | | [`Product Viewed`](/collect-data/tracking-plan/product-viewed.md) | `VIEW_CONTENT` | | | [`Checkout Started`](/collect-data/tracking-plan/checkout-started.md) | `START_CHECKOUT` | | | [`Products Searched`](/collect-data/tracking-plan/products-searched.md) | `SEARCH` | | | [`Payment Info Entered`](/collect-data/tracking-plan/payment-info-entered.md) | `ADD_BILLING` | | | [`Product Added to Wishlist`](/collect-data/tracking-plan/product-added-to-wishlist.md) | `ADD_TO_WISHLIST` | | | [`Signed Up`](/collect-data/tracking-plan/signed-up.md) | `SIGN_UP` | | | `Product List Viewed` | `LIST_VIEW` | | | `Product Shared` | `SHARE` | | | `Signed In` | `LOGIN` | | | `Application Installed` | `APP_INSTALL` | | | `Application Opened` | `APP_OPEN` | | Chord sends page and track events. Identify and screen events are not sent. A track event that is not in the table is skipped, and Chord logs it. Snap accepts only a fixed set of events. ## Common event fields These fields are included on every event sent to Snapchat. | Chord source (priority order) | Snap field | Notes | | --------------------------------------- | ------------------------- | ------------------------------------------ | | *(mapped from event — see table above)* | `event_name` | | | `timestamp` | `event_time` | | | `messageId` | `event_id` | Used for deduplication with the Snap Pixel | | `context.page.url` | `event_source_url` | | | *(hardcoded)* `false` | `data_processing_options` | | ## User data | Chord source (priority order) | Snap field | Notes | | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------- | ------------------------- | | `userId` > `anonymousId` | `external_id` | Array | | `properties.email` > `context.traits.email` > `traits.email` | `email` | | | `properties.phone` > `context.traits.phone` > `traits.phone` | `phone` | | | `properties.gender` > `context.traits.gender` > `traits.gender` | `gender` | | | `properties.first_name` > `context.traits.first_name` > `traits.first_name` | `firstName` | | | `properties.last_name` > `context.traits.last_name` > `traits.last_name` | `lastName` | | | `properties.birthday` > `context.traits.birthday` > `traits.birthday` | `birthday` | | | `city` from the address | `city` | | | `state` from the address | `state` | | | `zipcode` > `zip` > `postalCode` from the address | `zip` | | | `country` from the address | `country` | | | The IP address the server received > `context.ip` | `client_ip_address` | Not hashed | | `context.userAgent` | `client_user_agent` | Not hashed | | `context.device.advertisingId` | `madid` | Mobile ad ID | | `context.device.id` | `idfv` | iOS identifier for vendor | | `properties.click_id` > `integrations["Snap Conversions Api"].click_id` > `ScCid` query parameter from the page URL > `context.clientIds.sc_cid` | `sc_click_id` | Snap click ID | | `integrations["Snap Conversions Api"].uuid_c1` | `sc_cookie1` | Snap cookie value | The address is built from `properties.address`, `context.traits.address` and `traits.address`, one field at a time, in that order. ## Custom data These fields are sent in the `custom_data` block on all events. | Chord source (priority order) | Snap field | Notes | | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | | `properties.currency` > `properties.meta.i18n.currency` | `currency` | Defaults to `"USD"` | | `properties.value` > `properties.total` > `properties.price`, then the sum of each product's price times quantity | `value` | Total value after quantity. Defaults to `0` | | Count of products with a resolvable `item_id` | `num_items` | | | `properties.order_id` > `properties.orderId` > `properties.id` > `properties.cart_id` | `order_id` | Also sent as the top-level `transaction_id` | | `properties.query` > `properties.search_string` | `search_string` | | | The property of the same name | `sign_up_method`, `checkin_date`, `travel_start`, `travel_end`, `origin_airport`, `destination_airport`, `num_adults`, `num_children`, `country`, `city`, `region`, `postal_code` | Sent as is when present | ## Products Sent as a `products` array on events that include product data. Omitted if no products are present. | Chord source (priority order) | Snap field | Notes | | ------------------------------------------------------------- | --------------- | ---------------------------------- | | Configured field → `sku` → `variant_id` → `product_id` → `id` | `item_id` | Must match Item ID in Snap catalog | | `properties.products[].category` | `item_category` | | | `properties.products[].brand` | `brand` | | ## App data Events from mobile apps also carry these fields. | Chord source (priority order) | Snap field | Notes | | ------------------------------------------------------------------------- | ------------------------------------------------------------- | -------------------------------------- | | `context.device.adTrackingEnabled` | `advertiser_tracking_enabled`, `application_tracking_enabled` | | | `context.device.type` | `version` | `"i2"` for `ios`, `"a2"` for `android` | | `context.app.namespace` | `packageName` | | | `context.app.version` | `longVersion` | | | `context.os.version` | `osVersion` | | | `context.device.model` | `deviceName` | | | `context.locale` | `locale` | | | `context.network.carrier` | `carrier` | | | `context.screen.width`, `context.screen.height`, `context.screen.density` | `width`, `height`, `density` | | | `context.timezone` | `deviceTimezone` | | ## Deduplication Chord sends the Chord message ID as `client_dedup_id` on both the Snap Pixel and the Conversions API, and the order ID as `transaction_id`. See [Snap](/activate/event-streaming/destinations/advertising/snap.md#how-they-deduplicate) for how the two versions deduplicate. ## Testing and validation After connecting the destination: 1. Enable **Test Mode** in the destination settings to send events to Snapchat's `/validate` endpoint 2. Trigger test events and confirm they appear in the **Snap Events Manager debug tool** 3. Disable Test Mode before going live 4. After 24–48 hours, check **Events Manager > Diagnostics** to verify match rates and deduplication rates --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.chord.co/activate/event-streaming/destinations/advertising/snap/snap-conversions-api.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.