> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/snapchat.md).

# Snapchat

The two ways to send audiences to Snapchat, and why running both is usually right.

Two connectors send audiences to Snapchat. They reach different people, which is why they are usually deployed together.

## Which connector to use

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/snapchat/server-side.md"><strong>Server-side</strong></a></td><td>Sends offline hashed data straight from mediarithmics' servers to Snapchat, every time the segment is updated. Lets you control the segment name, description, source type and retention on the Snapchat side.</td></tr><tr><td><a href="/connectors/destinations/snapchat/pixel.md"><strong>Pixel</strong></a></td><td>Client-side. Fires the Snapchat pixel from the visitor's browser with an <code>event_tag</code>; mediarithmics sends no identifiers. The audience only grows from the moment the sync is set up.</td></tr></tbody></table>

{% hint style="info" %}
Setting up **both** is the recommendation. It maximises the match with Snapchat and so the performance of your targeting.
{% endhint %}

## What each connector sends

<table data-search="false"><thead><tr><th width="220">Connector</th><th width="180">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/snapchat/server-side.md">Server-side</a></td><td>Server-side</td><td>Email hash (SHA-256), Phone number, Mobile IDs</td></tr><tr><td><a href="/connectors/destinations/snapchat/pixel.md">Pixel</a></td><td>Client-side (pixel)</td><td>None</td></tr></tbody></table>

The server-side setup needs **Organisation Admin** rights on your Snapchat account, and its whitelisting code expires after 10 minutes - coordinate with your account team before starting.

## Partner documentation

Snapchat documents its own platform at <https://businesshelp.snapchat.com/s/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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.mediarithmics.io/connectors/destinations/snapchat.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.