CONNECTIONS / OneDrive / OneDrive to Meta Offline CAPI
From OneDrive files to Meta's offline optimization.
Connect OneDrive and point Signals at your OneDrive 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.
- ● onedrive → meta.capi :: live
- > read closed_deals rows=69,340
- hash sha256(email,phone) consent=filtered
- route meta deliver
- ✓ delivered · 56,859 matched
WHAT THIS ENABLES
OneDrive to Meta Offline CAPI
OneDrive to Meta Offline CAPI: Signals reads your OneDrive 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 OneDrive 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 OneDrive files by teams sharing exports via OneDrive.
The click, the conversion, and the credit.
The conversion happens off Meta, away from any pixel. Here is how OneDrive closes the loop.
Built for the teams that own the number.
Teams sharing exports via OneDrive activating Meta's offline optimization straight from OneDrive files.
From kickoff to verified events.
-
Connect
Read-only OAuth access to the OneDrive folder you name to feed Meta's Offline Conversions API, sized for Meta's 62-day event window.
-
Map
Signals picks up your OneDrive 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 OneDrive 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 OneDrive records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /offline_conversions source=microsoft-onedrive.closed_deals
- event_name "Purchase" · event_time 2026-07-19T20:40:20
- value 15690.00 · currency AED
- em sha256 "1fa603…" · ph sha256 "eb2201…" · external_id "txn-98620"
- ✓ accepted match=82%
Adjacent moves on the same stack.
from OneDrive
OneDrive to Google OCI
OneDrive to Google Offline Conversions: Signals reads your OneDrive files and reconciles…
Learn morefrom OneDrive
OneDrive to Google Store Sales
OneDrive to Google Store Sales: Signals reads your OneDrive files and matches in-person…
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 OneDrive Meta Offline CAPI sync run?
The pace follows your OneDrive files: Signals sends changes from OneDrive to Meta each time a new file lands. Because it processes only the newly dropped file, in-store and phone revenue joining Meta's optimization loop stays current while teams sharing exports via OneDrive keep Meta's 62-day event window in view. Delivery needs no export and no manual upload.
What match rate should a OneDrive-sourced Meta Offline CAPI batch expect?
Coverage of hashed identifiers across your OneDrive files decides it, and teams sharing exports via OneDrive own that inside OneDrive. A live email or phone matches into Meta; neither, and it will not. First-run feedback flags Meta's 62-day event window, which teams sharing exports via OneDrive then raise inside your OneDrive files.
NEXT STEP