DestinationActivation

Snapchat Conversions API

Snapchat uses Meta's identity vocabulary: email, phone, name, city, zip and the rest, all hashed. The platform assembles that set automatically from the identity graph — more fields, better match rates, lower cost per result.

Connect now Read the docs

Data delivered

Standard Snapchat events (PURCHASE, SIGN_UP, ADD_CART…) plus custom
The 11 hashed identity fields + IP and user agent
Value, currency and properties

What it is for

What you can do with it

Optimize campaigns on the real sale, not the click
Reuse the same identity mapping that already feeds Meta CAPI
Validate without polluting the account: test mode uses their validation endpoint

Why integrate

The business reason, not just the tech

Match rate is the metric that moves your CPA

The more identity fields arrive with a conversion, the more people Snapchat can match — and the better it optimizes. We send the 11 Meta-family fields (email, phone, name, city…) assembled from the graph, no manual mapping.

Validate before you spend

Test mode uses Snapchat's official validation endpoint: you check the accepted payload without polluting the account or the campaign history.

Reuse work already done

If your purchase event is already defined for another destination, enabling Snapchat means reusing the same event with another destination — minutes, not a project.

How to connect

Step by step

Step 1
Create the destination and paste your ad account credentials.
Step 2
Create a Delivery: pick the source event, filter and map the fields.
Step 3
Fire the first delivery in test mode and check it in the ads manager.

Frequently asked questions

Which identity fields are sent?

The same as Meta CAPI: email, phone, first and last name, gender, birthdate, city, state, zip, country and external id — hashed — plus IP and user agent in plain text, as the platform requires.