> 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.md).

# Snap

Snap runs Snapchat ads. Chord sends your events to Snapchat from the browser and from the server. Use both for the best coverage.

## What each version does

* [**Snap Pixel**](/activate/event-streaming/destinations/advertising/snap/snap-pixel.md) runs in the shopper's browser. It catches on-page behavior such as product views and add-to-cart clicks.
* [**Snap Conversions API**](/activate/event-streaming/destinations/advertising/snap/snap-conversions-api.md) runs on Chord's servers. It still reports conversions when a shopper has an ad blocker or closes the tab early.

## Why use both

The browser version sees what shoppers do on the page. The server version survives ad blockers and closed tabs. Together they give Snapchat more complete data.

## How they deduplicate

Both versions send the Chord message ID as `client_dedup_id`. Snapchat uses it to count each event once. For purchases, both also send the order ID as `transaction_id`, and Snapchat deduplicates on that as well.

If you use both destinations, set **Product Content ID Field** to the same value in each, so item IDs match.

## Set up

* [Snap Pixel](/activate/event-streaming/destinations/advertising/snap/snap-pixel.md)
* [Snap Conversions API](/activate/event-streaming/destinations/advertising/snap/snap-conversions-api.md)


---

# 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.md?ask=<question>&goal=<user_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.