This guide covers Pinterest Snapchat Conversions API setup for an online store: what you connect, in what order, what each platform actually receives, and where matching stays weaker than it does on Meta or Google. It is written for merchants and media buyers who want purchases to reach both platforms from the server, without building a Google Tag Manager container.
The setup uses SyncBeacon as the relay. Your store sends confirmed orders to SyncBeacon, and SyncBeacon forwards them to Pinterest and Snapchat. The same approach is described in more depth on the server-side tracking pillar page.
Why send Pinterest and Snapchat events from the server
Pinterest and Snapchat both ship a browser tag. Like every browser tag, it only reports what the visitor's browser lets it report. Ad blockers, Safari and iOS privacy features, and cookie banners all remove events before they leave the page. On a thank-you page that means a real order that never shows up in the ad platform.
A server-side connection reads the order from your store instead. A Shopify order webhook, a WooCommerce webhook or a Shopware Admin API sync does not depend on the shopper's browser, theme or payment method. The platform sees the purchase whether or not the browser tag ran.
Pinterest and Snapchat are smaller budget lines for many stores than Meta and Google, which is exactly why they often get the least tracking attention. Both are in SyncBeacon's launch destinations, next to Meta and Google Ads. If you are only on those two, the Meta setup guide covers the same ground.
What you need before you start
| Item | Snapchat | |
|---|---|---|
| Account in the platform | Pinterest ad account | Snapchat ad account with a Snap Pixel |
| Sign-in method in SyncBeacon | Pinterest OAuth | Snapchat OAuth |
| ID you enter | Ad Account ID | Pixel ID |
| Deduplication key | Event ID | Event ID |
You also need a SyncBeacon account with your store connected. If you are on the free Pilot plan, note that it includes one ad platform, so pick the one you want to test first. Current plan limits are on the pricing page.
Step 1: Connect your store
Purchases are the events Pinterest and Snapchat care about most, and they come from your store, so connect it first. How you do that depends on the platform:
- Shopify: connect with OAuth. SyncBeacon registers the order webhooks for you. Purchases, cancellations and the checkout-created event arrive server-side. Browser events such as page views and add to cart come from a theme app embed, and detection varies by theme.
- WooCommerce: install the free SyncBeacon plugin and authorize through WooCommerce's own screen. Orders arrive as signed webhooks. The plugin needs WordPress 6.0+, WooCommerce 7.0+ and PHP 7.4+.
- Shopware 6: create an integration in Shopware and paste its access key into SyncBeacon. Orders are polled through the Admin API about every two minutes. Instant webhooks are optional and need a Shopware plan that includes Flow Builder "Call URL".
Optionally, add the SyncBeacon browser script. It captures click IDs from the landing URL and keeps them until the order arrives, which matters most for Snapchat (see the matching section below). The script is a convenience, not a requirement for server-side purchases.
Step 2: Pinterest Conversions API setup
Pinterest CAPI is Pinterest's server-to-server endpoint for conversions. SyncBeacon sends to version 5 of it. In the SyncBeacon dashboard:
- Open Integrations and choose Pinterest.
- Sign in with Pinterest and approve the connection.
- Enter your Pinterest Ad Account ID.
- Save, then place a test order on your store.
That is the whole connection. There is no access token to copy and no container to deploy. If the credentials are rejected or the account ID is wrong, the error is a permanent one and the event is not retried. You will see it on the Conversions page against that event.
SyncBeacon maps a purchase to the matching Pinterest conversion event. Check the event name that shows up in Pinterest's own reporting after your test order rather than assuming one, because Pinterest's naming is theirs to change.
Step 3: Snapchat Conversions API setup
Snap CAPI is Snapchat's Conversions API. SyncBeacon uses version 3. The connection looks the same as Pinterest:
- Open Integrations and choose Snapchat.
- Sign in with Snapchat and approve the connection.
- Enter your Snap Pixel ID.
- Save, then place a test order.
The Snapchat connector can also send the Snap click ID when it was captured, and the _scid cookie when it exists. That is why the optional browser script is worth installing for Snapchat specifically.
What each platform receives
| Data | Snapchat | |
|---|---|---|
| Hashed email (SHA-256) | Yes | Yes |
| Hashed phone (SHA-256) | Yes | Yes |
| Order value and currency | Yes | Yes |
| Event ID for deduplication | Yes | Yes |
| Snap click ID | Not applicable | When captured |
| Pinterest click ID (epik) | No, not sent | Not applicable |
| IP address and user agent | Not sent | Yes, when consent allows |
| Snap cookie (_scid) | Not applicable | When present |
Email and phone are hashed before the event is stored or forwarded. Hashing is pseudonymisation, not anonymisation, so the data is still treated as personal data for GDPR purposes. See the GDPR page for how SyncBeacon handles consent.
Matching limits, stated plainly
This is the part most setup guides skip. Pinterest and Snapchat can only attribute a conversion to an ad if they can match the event to a user. What SyncBeacon has to offer them differs by platform:
SyncBeacon does not send the Pinterest click ID or the visitor's IP address and user agent. Matching rests on hashed email and phone. For a guest checkout without a phone number, that is a single identifier. If a Pinterest event comes through with no email and no phone, there is very little to match on.
Snapchat
Snapchat gets more signals: the Snap click ID, the cookie, IP address and user agent, plus hashed email and phone. But the click ID is only captured when the landing URL carries the sclid parameter, and IP and user agent are marketing identifiers. When marketing consent is missing, SyncBeacon strips them from the payload.
Consent changes what is forwarded
If a visitor explicitly denies marketing consent through a detected banner (Cookiebot, OneTrust, IAB TCF v2 or a manual override), the event is stored for your records and not forwarded to any ad platform. Without a banner, your own consent setting decides whether identifiers are used. When identifiers are stripped, some connectors skip the event instead of sending a thin one.
Two more limits worth knowing. Refunds and cancellations are not synced to ad platforms as adjustments, so reported revenue in Pinterest and Snapchat will not net out returns. And there is no promise that any given share of orders will be matched; that depends on how many of your shoppers provide an email or phone number.
Keeping your browser tags: deduplication
You do not have to remove the Pinterest tag or the Snap Pixel. Both platforms deduplicate a browser event and a server event that share the same event ID. SyncBeacon merges its own browser and server events for the same order. Shopify purchases use the order ID as the event ID.
Pixel-side deduplication has one condition: your own browser tag has to send the same ID. If it does not, both events can be counted. Test this before you scale spend. The technical deep dive explains how event IDs work end to end.
How to verify the setup
- Place a test order on your store with a real email address.
- In SyncBeacon, open Conversions and find the order. Each destination shows its own delivery status, and failures are listed per platform.
- In Pinterest and Snapchat, open the conversion or events view and confirm the purchase arrived with the value and currency you expect.
- Where the platform shows an event source, check that the purchase is listed as a server event.
Failed deliveries retry automatically, up to 24 attempts per destination, with backoff. Permanent errors such as bad credentials or invalid input stop immediately and show up as an error instead of a retry.
Platform reports can lag behind your store, and attribution windows are set by each platform. Compare orders in your store with events received, not with the platform's attributed revenue.
Common problems
| Symptom | Likely cause |
|---|---|
| No event in the platform, error in Conversions | Rejected credentials or wrong Ad Account ID / Pixel ID |
| Event stored but not forwarded | Visitor denied marketing consent, or the connector skipped an event with no identifiers |
| Low match rate on Pinterest | Guest orders without phone numbers; Pinterest click ID is not sent |
| Conversions counted twice | Browser tag is not reusing the same event ID |
Questions people ask
Do I need Google Tag Manager?
No. SyncBeacon reads store orders directly, so there is no web or server container to maintain. If you already run GTM, the browser tags can stay as they are. See the GTM alternative page for the trade-offs.
Is the connection the same on all three store platforms?
The destination setup is identical. Only the source step differs (Shopify OAuth, WooCommerce plugin, Shopware integration key).
Can I send to Pinterest, Snapchat and Meta at once?
Yes, on paid plans every ad platform is included. The same order is delivered once per destination and tracked separately, so one failing platform does not block the others.
Related reading
- Pinterest Conversions API and Snapchat Conversions API destination pages
- Server-side tracking explained
- Meta Conversions API without a developer
- Multi-touch attribution for ecommerce
- Free tracking audit
Get started
Close your conversion gap today
Connect Meta CAPI, Google Enhanced Conversions, and more - in one setup, no developer required.
Not legal advice. Consent and data-protection requirements depend on your jurisdiction and setup. SyncBeacon is GDPR-ready and EU-hosted, but ad platforms process data under their own terms, including outside the EU.