Connecting Square Online to Snapchat
Square Online orders settle into the same Square account as the card taken at the counter, which is a genuine advantage: the online and in-person halves of the business are already denominated in one ledger. Snapchat's audience is young, almost entirely mobile and inside an in-app browser, which is the least forgiving environment for browser-based tracking anywhere in paid media. The join between them succeeds or fails on one thing: whether the ScCid click identifier reaches the Square Online order before the conversion happens, because Snapchat can only match a conversion it can tie back to a click it recognizes.
Free30 minutesNo obligation
Specific to this pair
Square Online to Snapchat: food orders from the in-app browser
Square Online food orders often finish in Snapchat's in-app browser before a confirmation pixel loads, so send PURCHASE server-side from Square's order and payment webhooks, filtered to the online channel, to Snapchat's Conversions API. Use hashed phone from pickup orders as a key match, plus hashed email and any ScCid, with subtotal net of tips and tax.
Snapchat fits Square Online restaurants and cafes near campuses and younger neighborhoods, where ordering happens on a phone. The order is placed inside Snapchat's in-app browser, often in under two minutes, and the checkout may hand off to a Square-hosted payment page. Any pixel event that depends on a confirmation page loading in the webview will miss buyers who close Snapchat as soon as payment goes through.
Send PURCHASE server-side from Square's records instead: Square offers webhooks for orders and payments, so filter them to the online channel and send each completed online order to Snapchat's Conversions API. Pickup orders almost always carry a phone number for ready texts, and a hashed phone is one of Snapchat's stronger match keys on this traffic, often stronger than a ScCid that did not survive the webview. Add hashed email when present, and the ScCid if you captured it on your custom domain before the handoff.
Value matters for food. Send the subtotal net of tips and tax, and note that delivery orders placed through third-party apps are not Square Online orders at all; they will not appear in this feed and should not be counted against Snapchat spend.
Square Online → Snapchat · what breaks
Why this join usually fails — Square Online → Snapchat
- 01
The ScCid click identifier never reaches Square Online
Square Online sites are frequently on a Square-provided domain, and checkout may hand off to Square-hosted payment pages depending on configuration.
- 02
Counter sales counted as online conversions
The convenience of one ledger is also the trap. If the sales channel is not filtered, every card swipe at the register lands in your ad reporting as a conversion you paid for.
- 03
The in-app browser loses the identifier
Snapchat traffic arrives through a webview with inconsistent storage. Anything relying on the identifier still being in the browser at conversion time will lose a large share, and the loss is invisible unless you measure capture on Snapchat traffic specifically.
- 04
Nothing reconciles afterwards
Snapchat Ads Manager shows received and matched events. Arriving is not the test — deduplicated and matched is. Reconcile against your own records for the same window.
Square Online → Snapchat · the fix
What working looks like — Square Online → Snapchat
The ScCid click identifier on every order
Conversions arriving in Snapchat
Events appear in Snapchat Ads Manager, deduplicated against the pixel, and become usable for optimization.
Reconciled against the source
Square Online → Snapchat · architecture
How Square Online and Snapchat actually connect
- 1
Square Online holds the truth
The filter is the whole job. Square's default reporting cheerfully sums counter sales and online orders, and that total is not something any ad platform should be optimizing toward.
- 2
Snapchat needs a click to match
Snapchat matches server events on the click identifier and hashed customer information. Send both — on this traffic the fallback carries a meaningful share of the events.
- 3
The identifier is the bridge
The ScCid click identifier, captured at the visit and carried into the Square Online order.
- 4
The event source decides reliability
Send net of tips and taxes. Tips on food orders are substantial and are not your revenue.
- 5
Deduplication at the destination
Snapchat deduplicates on a client-supplied event identifier shared between the pixel and the Conversions API, the same pattern as Meta. Mismatched identifiers mean double counting.
Square Online → Snapchat · normal or broken
Working vs. broken, side by side — Square Online → Snapchat
Normal, not a fault
The ScCid click identifier present on the order
Sent from the Square transaction record
Deduplicated correctly
Snapchat deduplicates on a client-supplied event identifier shared between the pixel and the Conversions API, the same pattern as Meta. Mismatched identifiers mean double counting.
Reconciles with the source
Actually broken
The ScCid click identifier missing on most records
Square Online sites are frequently on a Square-provided domain, and checkout may hand off to Square-hosted payment pages depending on configuration.
Sent from the browser
The convenience of one ledger is also the trap. If the sales channel is not filtered, every card swipe at the register lands in your ad reporting as a conversion you paid for.
Counted twice, or not at all
Snapchat traffic arrives through a webview with inconsistent storage. Anything relying on the identifier still being in the browser at conversion time will lose a large share, and the loss is invisible unless you measure capture on Snapchat traffic specifically.
Nobody has reconciled it
Square Online → Snapchat · diagnose
Diagnostic order — Square Online → Snapchat
- 01
Count orders carrying the ScCid click identifier
- 02
Follow one real conversion end to end
- 03
Filter by sales channel and re-check the total
Compare the filtered online total against Square Online's own order count. If they disagree, the filter is wrong before the tracking is.
- 04
Measure capture rate on Snapchat traffic alone
The in-app browser is the failure case, so a healthy overall rate can hide a poor one on precisely the traffic you are paying for.
- 05
Read the match rate, not the success message
Snapchat Ads Manager shows received and matched events. Arriving is not the test — deduplicated and matched is. Reconcile against your own records for the same window.
Square Online → Snapchat · prove
How it gets proven — Square Online → Snapchat
Source of truth
Square transactions filtered to the online sales channel, by location.
- The ScCid click identifier confirmed present on a live order.
- Capture rate measured on Snapchat traffic specifically, and deduplication confirmed on a real conversion.
- Online-channel transactions reconciled against imported conversions for a settled week.
Square Online → Snapchat · free audit
What we check in the free audit
- Count orders carrying the ScCid click identifier
- Follow one real conversion end to end
- Filter by sales channel and re-check the total
- Measure capture rate on Snapchat traffic alone
- Read the match rate, not the success message
Checked against
Square transactions filtered to the online sales channel, by location.
Free30 minutesNo obligation
Square Online → Snapchat · when not to buy
When you don't need this — Square Online → Snapchat
- Measure identifier coverage yourself first — pull your last hundred orders and count how many carry the ScCid click identifier.
- If Square Online is a small side channel next to your counter business, measure it on order count and do not build an import for it.
- If your customers are not in Snapchat's age profile, the channel is the wrong question and no measurement work fixes that.
Square Online → Snapchat · what we deliver
What gets built — Square Online → Snapchat
Identifier capture into Square Online
Persist the identifier in first-party storage on your own domain before the handoff, and reattach it to the order at the point the transaction is written.
Event source: the Square transaction record
Send net of tips and taxes. Tips on food orders are substantial and are not your revenue.
Dispatch to Snapchat
Server events to the Snapchat Conversions API with the click identifier, hashed customer data and a matched event identifier.
Reversals where they exist
Refunds appear in Square as their own records and should be sent as reversals.
Written guarantee
95%+ tracking accuracy
Measured against Square transactions filtered to the online sales channel, by location.. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Square Online → Snapchat questions, answered
Buyers often close the in-app browser before any confirmation page loads. Send online orders server-side from Square's order or payment webhooks.
Hashed phone from pickup orders, hashed email when present, and the ScCid if your domain captured it before checkout.
Almost always because the ScCid click identifier never reached the Square Online order. Square Online sites are frequently on a Square-provided domain, and checkout may hand off to Square-hosted payment pages depending on configuration. Measure coverage before debugging the dispatch.
Snapchat's click identifier, appended to your landing page URL. Snapchat also matches on hashed email, phone and mobile advertising IDs. The environment is the problem: traffic arrives inside Snapchat's in-app browser, whose storage behaviour is inconsistent, so an identifier that is captured but not immediately persisted server-side often is not there by the time the conversion happens.
The Square transaction record. Send net of tips and taxes. Tips on food orders are substantial and are not your revenue.
Snapchat Ads Manager shows received and matched events. Arriving is not the test — deduplicated and matched is. Reconcile against your own records for the same window.
More on Square Online → Snapchat
- Square → SnapchatConnecting Square to Snapchat
- Square Online → Google AdsConnecting Square Online to Google Ads
- Square Online → MetaConnecting Square Online to Meta Conversions API
RELATED GUIDES
Where Square Online → Snapchat fits in the rest of your tracking
- Snapchat · CateringSnapchat Ads conversion tracking for catering companies
- Snapchat · RestaurantsSnapchat Ads conversion tracking for restaurants
- Snapchat × POS SystemHow to reconcile Snapchat Ads against your point-of-sale system
- Snapchat · Reactivation → repeat purchaseHow to track lapsed customer reactivation to repeat purchase for Snapchat Ads
- Deliverect → SnapchatConnecting Deliverect to Snapchat
- Square Online → RedditConnecting Square Online to Reddit
- CateringConversion tracking for catering, measured in confirmed events
- Popmenu → SnapchatConnecting Popmenu to Snapchat
Free · 30 min
Get Square Online and Snapchat joined properly
WhatsAppFree30 minutesNo obligation
