# Snapchat Ads

> Send server-to-server conversion events to Snapchat Ads through the Snap Conversions API, built for HIPAA-regulated workflows.

Source: https://docs.oursprivacy.com/docs/snapchat-ads

[Open Destinations in app](https://app.oursprivacy.com/destinations)

Send conversions to Snapchat Ads through the Snap Conversions API. Ours Privacy routes events server-to-server so Snapchat never interacts directly with your visitors' browsers, and gives you control over which fields are redacted or hashed before they leave.

Ours Privacy automatically captures Snapchat click IDs from the URL and reuses them on subsequent events, so attribution survives navigation across your site.

***

## Configuring a Snapchat destination

Open [Destinations](https://app.oursprivacy.com/destinations), click **Add destination**, and select Snapchat. Paste in your **Pixel ID** and **Snapchat Conversion API Key**.

### Find your Pixel ID

1. Go to Snapchat Ads Manager.
2. Navigate to **Settings** > **Pixel**.
3. Copy the Pixel ID from the list and paste it into the destination configuration.

### Find your Snapchat Conversion API Key

1. In Snapchat Ads Manager, go to **Settings** > **Pixel**.
2. Select your pixel and open the **Conversion API** section.
3. Generate an access token if you don't already have one.
4. Copy the token and paste it into the destination configuration.

***

## Snapchat only accepts a fixed list of event names

> **Important:** Snapchat's Conversions API only accepts a fixed set of event names. Events sent with any other name are rejected by Snapchat. They will not appear in Ads Manager and will not be attributed to your campaigns.

A few examples of the accepted names:

* `PURCHASE`
* `SIGN_UP`
* `PAGE_VIEW`
* `VIEW_CONTENT`
* `ADD_CART`
* `START_CHECKOUT`
* etc.

You can see the full list in the destination configuration in app when you map your events, or in Snap's [Conversions API parameters documentation](https://developers.snap.com/api/marketing-api/Conversions-API/Parameters).

### How to send the right name

You have two options:

1. **Match the name when you track.** If you call `ours('track', 'PURCHASE', ...)` directly, it passes through to Snapchat unchanged.
2. **Rename the event in the destination.** If your tracked event is called something else (e.g. `purchase`, `Order Completed`, `account_created`), use the rename option on the Snapchat destination to map it to one of Snap's accepted values.

### What to do for events that don't match

Snapchat reserves `CUSTOM_EVENT_1` through `CUSTOM_EVENT_5` for events that don't fit the standard set. If you have an event that isn't covered, such as a product-specific milestone, rename it to one of the `CUSTOM_EVENT_*` slots in the destination configuration.

```javascript
// Track using a name your team understands:
ours('track', 'demo_requested', { plan: 'pro' });

// Then in the Snapchat destination, rename `demo_requested` → `CUSTOM_EVENT_1`.
```

***

## Limited Data Use (LMU)

Snapchat's version of the Limited Data Use flag is called Limited Match Use, and it restricts how Snapchat may process an event. Advertisers typically apply it to people covered by US state privacy laws such as the CCPA.

Map the **Data Processing Options** field in the destination mapping. It takes a list, and accepts two values:

* `LMU`: process the event under Limited Match Use.
* `DELETE`: treat the event as a deletion request for that person's data.

Any other value is ignored. Map the field to the opt-out signal you already collect, such as a consent choice or a [Global Privacy Control](https://docs.oursprivacy.com/docs/cookie-consent/global-privacy-control) signal. Leave it unmapped and events are sent with no restriction requested.

Setting `LMU` restricts what Snapchat may do with the event; it does not stop the event from being sent. To withhold events entirely, use [Global Data Governance](https://docs.oursprivacy.com/docs/global-data-governance) rules or your consent configuration.

See [Limited Data Use](https://docs.oursprivacy.com/docs/destination-overview#limited-data-use-ldu) for the destinations that support this and how the flag fits your consent setup.

***

## Next Steps

* [Send and Track Allowed Events](https://docs.oursprivacy.com/docs/allow-listing-events): define which events are tracked.
* [Destinations](https://docs.oursprivacy.com/docs/destination-overview): overview of all available destinations.

Need help? Email [support@oursprivacy.com](mailto:support@oursprivacy.com).
