CONNECTIONS / FTP / FTP to Snap Offline CAPI
Your FTP drops, wired to Snapchat in-store conversions.
Signals reads your FTP drops through read-only credentials scoped to the SFTP path you name, then reports in-store purchases against the Snapchat campaigns that reached the buyer so Snapchat sees offline conversions without an export.
- ● ftp → snap.capi :: live
- > read closed_deals rows=52,417
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ delivered · 42,982 matched
WHAT THIS ENABLES
FTP to Snapchat Offline CAPI
FTP to Snapchat Offline CAPI: your FTP 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.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, reading your FTP drops each time a new file lands.
- In-person conversions Snapchat can bid on, with no export step out of your FTP drops.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how FTP closes the loop.
Built for the teams that own the number.
Teams exporting nightly to SFTP who need physical-world sales counted inside Snapchat performance out of FTP drops.
From kickoff to verified events.
-
Connect
Read-only credentials scoped to the SFTP path you name, mapped to Snapchat's Conversions API and tuned for offline event timing.
-
Map
Columns from your FTP drops align to Snapchat's Conversions API in the visual mapper, hashed as the file lands and checked for offline event timing.
-
Deliver
Each time a new file lands, Signals reads your FTP drops and reports in-store purchases against the Snapchat campaigns that reached the buyer, processes only the newly dropped file, with offline event timing watched 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 FTP records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=ftp.closed_deals
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784630204 · price 25575 · currency AED
- ✓ accepted · match=true
Adjacent moves on the same stack.
from FTP
FTP to Google OCI
FTP to Google Offline Conversions: your FTP drops, hashed and consent-checked, feed Google…
Learn morefrom FTP
FTP to Google Store Sales
FTP to Google Store Sales: your FTP drops, hashed and consent-checked, feed Google Ads as…
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 FTP Snap Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into Snapchat. Since Signals processes only the newly dropped file, physical-world sales counted inside Snapchat performance keeps pace and teams exporting nightly to SFTP watch offline event timing. One scoped connection sets it up, cadence adjustable later.
What match rate should a FTP-sourced Snap Offline CAPI batch expect?
Match rate follows identifier coverage in your FTP drops, which teams exporting nightly to SFTP control, not FTP 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 teams exporting nightly to SFTP tune against.
NEXT STEP