CONNECTIONS / Box / Box to Meta Offline CAPI
Your Box files, wired to Meta's offline optimization.
Connect Box and point Signals at your Box files; it credits dealer, branch, and phone sales to the Meta campaigns behind them each time a new file lands, hashed and consent-checked for Meta.
- ● box → meta.capi :: live
- > read closed_deals rows=51,116
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 43,960 matched
WHAT THIS ENABLES
Box to Meta Offline CAPI
Box to Meta Offline CAPI: Signals reads your Box files and credits dealer, branch, and phone sales to the Meta campaigns behind them, hashed and consent-checked each time a new file lands.
- Offline and in-store sales from your Box files activated for Meta, as Signals credits dealer, branch, and phone sales to the Meta campaigns behind them.
- In-store and phone revenue joining Meta's optimization loop, drawn from your Box files by ops teams sharing exports in Box.
The click, the conversion, and the credit.
The conversion happens off Meta, 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 Meta's offline optimization straight from Box files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the Box folder you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.
-
Map
Signals picks up your Box files, and its columns map to Meta's Offline Conversions API in the visual mapper, hashed and checked for Meta's 62-day event window.
-
Deliver
On each run, Signals pulls your Box files, credits dealer, branch, and phone sales to the Meta campaigns behind them, and processes only the newly dropped file, with Meta's 62-day event window 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 /offline_conversions source=box.closed_deals
- event_name "Purchase" · event_time 2026-07-19T20:08:12
- value 37961.00 · currency AED
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-81692"
- ✓ accepted match=86%
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 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 Box Meta 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 Meta on that cadence. Each run processes only the newly dropped file, so campaign learning fed by real-world purchases holds up on Meta's 62-day event window. The live debugger confirms every delivery inline.
What match rate should a Box-sourced Meta 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 Meta; one missing both cannot. First-run feedback from Offline Conversions API pinpoints Meta's 62-day event window, the number ops teams sharing exports in Box tune against.
NEXT STEP