CONNECTIONS / File drops / File drops to Snap Offline CAPI
Your file drops, wired to Snapchat in-store conversions.
Connect File drops and point Signals at your file drops; 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.
- ● file drops → snap.capi :: live
- > read closed_deals rows=62,576
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 51,938 matched
WHAT THIS ENABLES
File drops to Snapchat Offline CAPI
File drops to Snapchat Offline CAPI: your file drops, hashed and consent-checked, feed Snapchat as Signals reports in-store purchases against the Snapchat campaigns that reached the buyer each time a new file lands.
- Offline and in-store sales from your file drops 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 file drops by teams landing POS and back-office exports as files.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how File drops closes the loop.
Built for the teams that own the number.
Teams landing POS and back-office exports as files activating Snapchat in-store conversions straight from file drops.
From kickoff to verified events.
-
Connect
Read-only access to the SFTP, S3, or GCS drop you name to feed Snapchat's Conversions API, sized for offline event timing.
-
Map
Signals picks up your file drops, 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 file drops, 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 File drops records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=files.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784320293 · price 33424 · currency USD
- ✓ accepted · match=true
Adjacent moves on the same stack.
from File drops
File drops to Google OCI
File drops to Google Offline Conversions: your file drops, hashed and consent-checked, feed…
Learn morefrom File drops
Files to Google Store Sales
POS and SFTP files to Google Store Sales validates and hashes each nightly export the…
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 File drops Snap Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly File drops sync of your file drops into Snapchat. Since Signals processes only the newly dropped file, physical-world sales counted inside Snapchat performance keeps pace and teams landing POS and back-office exports as files watch offline event timing. One scoped connection sets it up, cadence adjustable later.
What match rate should a File drops-sourced Snap Offline CAPI batch expect?
In File drops, match rate tracks the email and phone quality your file drops carry. Clean identifiers land for Snapchat; blank ones never will. The first Conversions API report shows teams landing POS and back-office exports as files where offline event timing needs work, a data-quality task handled in File drops.
NEXT STEP