CONNECTIONS / FTP / FTP to Meta Offline CAPI
Your FTP drops, wired to Meta's offline optimization.
Signals reads your FTP drops through read-only credentials scoped to the SFTP path you name, then credits dealer, branch, and phone sales to the Meta campaigns behind them so Meta sees offline conversions without an export.
- ● ftp → meta.capi :: live
- > read closed_deals rows=23,131
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 19,661 matched
WHAT THIS ENABLES
FTP to Meta Offline CAPI
FTP to Meta Offline CAPI: your FTP drops, hashed and consent-checked, feed Meta as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands.
- Signals credits dealer, branch, and phone sales to the Meta campaigns behind them, reading your FTP drops each time a new file lands.
- Campaign learning fed by real-world purchases, with no export step out of your FTP drops.
The click, the conversion, and the credit.
The conversion happens off Meta, 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 in-store and phone revenue joining Meta's optimization loop out of FTP drops.
From kickoff to verified events.
-
Connect
Read-only credentials scoped to the SFTP path you name, mapped to Meta's Offline Conversions API and tuned for Meta's 62-day event window.
-
Map
Columns from your FTP drops align to Meta's Offline Conversions API in the visual mapper, hashed as the file lands and checked for Meta's 62-day event window.
-
Deliver
Each time a new file lands, Signals reads your FTP drops and credits dealer, branch, and phone sales to the Meta campaigns behind them, processes only the newly dropped file, with Meta's 62-day event window 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 /offline_conversions source=ftp.closed_deals
- event_name "Purchase" · event_time 2026-07-13T05:23:23
- value 40825.00 · currency SAR
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-44203"
- ✓ accepted match=85%
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 Meta Offline CAPI
ActiveCampaign to Meta Offline CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
Meta Offline CAPI
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to…
Learn moreAsked on almost every call.
How often does the FTP Meta Offline CAPI sync run?
You set the cadence, from near-real-time to a nightly FTP sync of your FTP drops into Meta. Since Signals processes only the newly dropped file, in-store and phone revenue joining Meta's optimization loop keeps pace and teams exporting nightly to SFTP watch Meta's 62-day event window. One scoped connection sets it up, cadence adjustable later.
What match rate should a FTP-sourced Meta 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number teams exporting nightly to SFTP tune against.
NEXT STEP