Meta Offline CAPI
Meta Offline CAPI, from source system to Ads Manager.
Datahash ingests offline transactions from your POS, CRM, or warehouse and routes them to Meta with hashed identifiers, event dedupe, and closed-loop match reporting.
- ● meta.offline_capi :: live
- > event offline_purchase value=12,750 AED
- hash sha256(em,ph,external_id) pii=cleared
- route offline_conversions match 58%
- ✓ delivered · offline event accepted
WHAT THIS ENABLES
Meta Offline CAPI
Meta Offline CAPI is the offering that takes conversions closed away from any Meta surface, in-store, over the phone, or in a back office, and delivers them to Meta's Offline Conversions API as hashed, deduplicated events.
- In-store, branch, and call-centre revenue counted in the same Ads Manager reporting as your web conversions.
- Meta optimization that learns from sales landing days or weeks after the click, alongside instant web events.
- Value-based bidding fed by real transaction amounts pulled from your source system.
Built for the teams that own the number.
Teams still uploading offline conversion CSVs to Meta by hand.
From kickoff to verified events.
-
Source
Connect via SFTP, S3, GCS, warehouse, or CRM sync.
-
Match
Hashed email, phone, and external ID prepared per Meta spec.
-
Deliver
Meta Offline Events API with your dataset and event set mapping.
-
Report
Closed-loop match rate reporting per upload.
WHAT FLOWS WHERE
One use case, every source.
An offline transaction lands in your backend, Signals hashes the identifiers and timestamps it at the moment of sale, then delivers it to Meta's Offline Conversions API.
An offline transaction lands in your backend, Signals hashes the identifiers and timestamps it at the moment of sale, then delivers it to Meta's Offline Conversions API.
What ships with this offering.
Offline conversions inside Meta campaign optimization.
Hashed, privacy-safe identifier handling end to end.
Match rate visibility per event set.
No more manual CSV uploads.
ON THE WIRE
What the platform actually receives.
Identifiers are hashed with SHA-256 at source. The payload the destination sees never contains raw PII.
- ● signals :: event payload
- > POST /{event_set}/events source=offline
- event_name "Purchase" · event_time 1789234512
- em sha256 "3f8b2a…" · ph sha256 "d41c90…"
- value 12750 · currency AED
- ✓ accepted · pii=hashed-at-ingestion
Measured in production.
3.2x
overall ROAS increase for Raymond with Meta Offline CAPI
1.9x
offline ROAS uplift for Raymond
80%
approximate drop in Raymond's cost per offline purchase
CASE STUDY
Raymond: 3.2x overall ROAS increase with Meta Offline CAPI.
Raymond runs this offering on Signals in production.
- > result raymond
- offering meta offline capi
- metric 3.2x overall ROAS increase with Meta Offline CAPI.
- ✓ measured in production
Adjacent moves on the same stack.
meta
Meta Web CAPI
Datahash is a Meta Business Partner. We set up Meta Conversions API on your website server-side, deduped with your existing Meta Pixel, hashed and privacy-safe.
Learn moremeta
Meta CAPI for CRM
Datahash ingests lead status from your CRM and sends Meta the qualified events it needs to optimize on lead value instead of lead volume.
Learn more
Google Store Sales
Datahash automates Store Sales Direct and Store Sales Customer Match uploads from your POS or warehouse into Google Ads.
Learn more
snap
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreBring it from where the data lives.
Every source that supports this use case. Pick a platform to see the exact setup.
CRM
Databases
Files / storage
Data warehouses
Datahash API
Custom
Questions your team will ask.
How are Meta Offline Events different from standard events?
Standard events come from your website or app in near real time. Offline events describe conversions that happened away from your digital properties, matched to people via hashed identifiers instead of browser signals. Meta attributes them back to ad exposure and uses them in optimization.
What is a good match rate?
It depends on identifier coverage. With clean email and phone present on most records, offline match rates of 40 to 70 percent are common for Meta Offline CAPI, lower than web because there is no pixel or browser signal to match against. Datahash baselines your source data during discovery and tells you what match rate to expect before go-live, then reports it per upload.
What if we do not have email or phone on every record?
Meta matches on the best combination of keys available per record, beyond email and phone. Name, city, zip code, date of birth, and external_id all contribute to the match, and Datahash maps whichever of these your source system holds for each transaction. More keys per record raise the match probability, so partial records still have a real chance of matching instead of being dropped.
NEXT STEP
Live in fifteen minutes. Measurable in a week.
Talk to our team of solutions engineers. We map your source data, propose an integration plan, and give you a live setup in the same call where possible.