Snapchat Ads

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 Open Destinations in app, click Add destination, and select Snapchat. Paste in your Pixel ID and Snapchat Conversion API Key, and you'll see "Your destination is configured and ready."

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.

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 — for example a product-specific milestone — rename it to one of the CUSTOM_EVENT_* slots in the destination configuration.

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

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

Next Steps

• Send and Track Allowed Events — define which events are tracked.
• Destinations — overview of all available destinations.

Need help? Email support@oursprivacy.com.