Home
Connectors
BigCommerce - Snapchat

Send every BigCommerce 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 BigCommerce 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.

Q: How long does it take to connect BigCommerce to Snapchat?

Most brands are live in under 20 minutes. Once BigCommerce is connected, every destination receives the same resolved events, Snapchat included.

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 BigCommerce event reaches Snapchat. Captured on the server, resolved to a person, then sent.

01 Capture

Captured from BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.

See the BigCommerce integration

BigCommerceWhat it sends

order_idBigCommerce order
email / phonecheckout contact
customer_idBigCommerce customer record
productscatalog items on the order
total_inc_taxorder value

02 Understand

Resolved to one person before it leaves

Every BigCommerce 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

BigCommerce's hosted checkout limits what a browser tag can see at the moment of purchase, which is exactly the moment that matters for conversion tracking.

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 BigCommerce feeds Snapchat. Two gains on the Snapchat side, two on the BigCommerce 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.

BigCommerce

Every event, server-side

Storefront and checkout events are captured from BigCommerce on the server, independent of the browser.

BigCommerce

One setup, every destination

Connect BigCommerce once and forward to every ad platform, email tool and warehouse you run.

Setup

Live in under 20 minutes.

You need admin access to your Snapchat Ads account.

Upstack dashboardExample

BigCommerce Data source Connected

Snapchat Destination Healthy

Read the full Snapchat setup guide

01

Connect BigCommerce

Server-side capture of BigCommerce storefront and checkout events, resolved and forwarded downstream.
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 BigCommerce 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 BigCommerce 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.