Home
Connectors
Custom stack - Snapchat

Send every Custom stack event to Snapchat, server-side

Q: Do I still need the Snap browser pixel?

Server-side delivery works on its own, but running both gives Snap the strongest signal. As long as the Snap Pixel ID matches between your browser pixel and the Upstack destination, Snapchat’s deduplication prevents double counting.

Q: What permissions does the Conversions API token need?

The token must have permission to send events on behalf of your ad account. Generate it with the minimum scope needed for sending conversion events: Upstack does not need management or spending permissions.

Q: Which customer parameters are sent to Snapchat?

Events carry hashed email and phone plus the Snap click ID (ScCid, or lowercase sccid, from the ad URL) when available.

Q: How do I check that Custom stack events are reaching Snapchat?

Upstack marks the destination Healthy, and Events Manager in Snapchat Ads Manager shows events from your Conversions API integration. Match quality and conversion attribution build over the following 24 to 48 hours.

Each event is resolved to a person against a 750M+ device graph before it reaches Snapchat, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

US device IDs in the graph: 750M+
Match rate on events: 90%+
Identity window, per customer: Lifetime
Most brands are live: <20 min

How it flows

How a Custom stack event reaches Snapchat. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.

See the Custom stack integration

Custom stackWhat it sends

event_namewhatever you choose to call it
user identifiersany of email, phone, external ID
value / currencyif the event carries revenue
custom propertiesany attribute in your own schema

02 Understand

Resolved to one person before it leaves

Every Custom stack event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.

How resolution works

Resolved before it is sent

IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.
DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to Snapchat

Send identity-resolved events to the Snapchat Conversions API with restored identifiers.

See the Snapchat integration

SnapchatWhat it receives

hashed email / phoneConversions API matching
click IDattribute the swipe
event_iddedupe
price / currencyvalue optimization

The catch

The freedom to name your own events is also the risk: an ad platform expects specific event names and parameter shapes, and anything outside that is accepted and ignored.

Mapping happens before send, not in the platform.

Where to check in SnapchatDelivery you can audit

Snapchat Ads Manager Events Manager

where Conversions API events are listed with their match status.

What changes

What changes when Custom stack feeds Snapchat. Two gains on the Snapchat side, two on the Custom stack side.

Snapchat

Server-side delivery

By default Upstack sends events to Snapchat from its servers as well as through the Snapchat tag, so an event an ad blocker or browser privacy setting stops in the browser still arrives from the server.

Snapchat

Identity-resolved events

Events sent to Snapchat carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.

Custom stack

Any stack, any framework

Headless, custom checkout, native app or a platform we haven’t listed: if it can make an HTTP request, it can send to Upstack.

Custom stack

The same event schema

Custom events are resolved, filtered and forwarded exactly like a Shopify order.

Setup

Post directly from your backend so nothing depends on the browser.

You need admin access to your Snapchat Ads account.

Upstack dashboardExample

Custom stack Data source Connected

Snapchat Destination Healthy

Read the full Snapchat setup guide

01

Connect Custom stack

Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02

Add the Snapchat destination

Under Destinations, add Snapchat with your Snap Pixel ID (a UUID) and a Conversion API Token generated on the Business Details page in Snapchat Business Manager, typically over 100 characters long.
03

Check events in Snap Events Manager

Upstack marks the destination Healthy, and Events Manager in Snapchat Ads Manager shows events from your Conversions API integration. Match quality and conversion attribution build over the following 24 to 48 hours.

FAQ

Questions about Custom stack and Snapchat.

Do I still need the Snap browser pixel?

Server-side delivery works on its own, but running both gives Snap the strongest signal. As long as the Snap Pixel ID matches between your browser pixel and the Upstack destination, Snapchat’s deduplication prevents double counting.

What permissions does the Conversions API token need?

The token must have permission to send events on behalf of your ad account. Generate it with the minimum scope needed for sending conversion events: Upstack does not need management or spending permissions.

Which customer parameters are sent to Snapchat?

Events carry hashed email and phone plus the Snap click ID (ScCid, or lowercase sccid, from the ad URL) when available.

How do I check that Custom stack events are reaching Snapchat?

Upstack marks the destination Healthy, and Events Manager in Snapchat Ads Manager shows events from your Conversions API integration. Match quality and conversion attribution build over the following 24 to 48 hours.