CONNECTIONS / Shopify / Shopify to Snap CAPI
Shopify checkouts, server-side to Snap.
A Snap Pixel that only sees what the browser lets through leaves gaps at the exact events campaigns optimize on. Signals fills them with a server-side feed of the same storefront checkout events, deduped against the Pixel.
- ● shopify → snap.web_capi :: live
- > event Checkout completed value=221.00 AED
- hash sha256(email,phone) dedupe=pixel+server
- route snap.web_capi match 69%
- ✓ delivered · event accepted
WHAT THIS ENABLES
Shopify to Snap Conversions API
Shopify to Snap Conversions API delivers checkout and purchase events from the storefront server-side to Snap, deduped against the Snap Pixel and enriched with hashed identifiers, so Snap's optimization keeps seeing sales the Pixel alone would miss.
- Purchase events reaching Snap even when the Pixel is blocked or delayed in-browser.
- Hashed first-party identifiers raising match rates beyond what browser-only tracking supports.
- Lower-funnel Snap campaigns optimizing on the full storefront event set, not a partial one.
WHAT FLOWS WHERE
Shopify to Web CAPI, mapped.
A Shopify checkout event is hashed by Signals and posted to Snap's Conversions API under the same event identifier the Pixel already carries, so Snap counts the sale once.
A Shopify checkout event is hashed by Signals and posted to Snap's Conversions API under the same event identifier the Pixel already carries, so Snap counts the sale once.
Built for the teams that own the number.
D2C brands running Snap alongside Meta and Google from the same checkout events.
From kickoff to verified events.
-
Install
Web Pixel added to the storefront theme, paired with app-scoped checkout webhook access.
-
Map
Storefront events matched to Snap's event taxonomy, with hashed identifiers attached at each step.
-
Deliver
Server-side delivery to Snap CAPI, deduped against the existing Pixel and confirmed in Snap Events Manager.
What ships with this use case.
Deduped Pixel-plus-server coverage on every checkout event that matters.
Higher match rates from hashed identifiers Snap's browser Pixel never sees.
Verified delivery visible in Snap Events Manager before campaigns rely on it.
What Web CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=shopify.checkout
- event_type "PURCHASE" · timestamp 1784516280
- hashed_email "2ac910…" · hashed_phone_number "e04b7f…"
- price 221.00 · currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Shopify
Shopify to every ad platform
Shopify to every ad platform is a single install that maps Shopify's order and checkout…
Learn morefrom Shopify
Shopify to Meta Click-to-Message
Shopify to Meta Click-to-Message Conversions ties a Shopify order back to the…
Learn more
same use case
BigCommerce to Snap CAPI
Snap Conversions API for BigCommerce: Signals posts checkout purchases to Snapchat…
Learn moregeneric
Snap Web CAPI
Datahash is a Snapchat Marketing Partner. We deliver Snap CAPI for web, deduped with the…
Learn moreAsked on almost every call.
Do we keep the Snap Pixel that came with Shopify's Snapchat channel?
Yes. The Pixel and the Conversions API feed run together, sharing an event identifier so Snap discards a duplicate rather than counting it twice. Removing the Pixel would only remove the client-side signal it still adds for events the server path is not built to duplicate.
Which Shopify events matter most for Snap's optimization?
Checkout completed and add to cart carry the most weight for Snap's lower-funnel bidding, since those events sit closest to a purchase decision. Signals prioritizes full-fidelity delivery on those two first, then extends server-side coverage to page view and product view as storefront volume and mapping time allow, without delaying the events campaigns depend on most.
NEXT STEP