CONNECTIONS / Box / Box to Snap Offline CAPI
Your Box files, wired to Snapchat in-store conversions.
Connect Box and point Signals at your Box files; it reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands, hashed and consent-checked for Snapchat.
- ● box → snap.capi :: live
- > read closed_deals rows=64,616
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 57,508 matched
WHAT THIS ENABLES
Box to Snapchat Offline CAPI
Box to Snapchat Offline CAPI: Signals reads your Box files and reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked each time a new file lands.
- Offline and in-store sales from your Box files activated for Snapchat, as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer.
- Physical-world sales counted inside Snapchat performance, drawn from your Box files by ops teams sharing exports in Box.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Box closes the loop.
Built for the teams that own the number.
Ops teams sharing exports in Box activating Snapchat in-store conversions straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals picks up your Box files, and its columns map to Snapchat's Conversions API in the visual mapper, hashed and checked for offline event timing.
-
Deliver
On each run, Signals pulls your Box files, reports in-store purchases against the Snapchat campaigns that reached the buyer, and processes only the newly dropped file, with offline event timing in the debugger.
What changes when the CSV goes away.
| Capability | Manual CSV upload | Datahash |
|---|---|---|
| Reporting | Offline sales sit in a separate export, reconciled by hand. | Revenue counted in the same Offline CAPI reporting as web conversions. |
| Deduplication | A re-uploaded file risks counting the same conversion twice. | Deduped delivery, so a resent record never counts as a second conversion. |
| Match visibility | Match quality is a guess until the numbers look off. | Match rate reported per upload, tied to the source event set that produced it. |
| Effort and latency | An analyst exports and uploads on a manual cadence. | Server-side and automatic the moment Box records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=box.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784217903 · price 46637 · currency SAR
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Box
Box to Google OCI
Box to Google Offline Conversions: Signals reads your Box files and reconciles closed-won…
Learn morefrom Box
Box to Google Store Sales
Box to Google Store Sales: Signals reads your Box files and matches in-person transactions…
Learn more
same use case
ActiveCampaign to Snap Offline CAPI
ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreAsked on almost every call.
How often does the Box Snap Offline CAPI sync run?
Delivery tracks Box, run by ops teams sharing exports in Box: a near-real-time or scheduled sync of your Box files feeds Snapchat on that cadence. Each run processes only the newly dropped file, so in-person conversions Snapchat can bid on holds up on offline event timing. The live debugger confirms every delivery inline.
What match rate should a Box-sourced Snap Offline CAPI batch expect?
Match rate follows identifier coverage in your Box files, which ops teams sharing exports in Box control, not Box itself. A record with a current hashed email or phone matches for Snapchat; one missing both cannot. First-run feedback from Conversions API pinpoints offline event timing, the number ops teams sharing exports in Box tune against.
NEXT STEP