Snap Offline CAPI
Snap campaigns learning from what happens offline.
Deliver offline conversions to Snap on a schedule that fits your operations.
- ● snap.offline_capi :: live
- > batch offline_sales rows=8,940
- hash sha256(em,ph) pii=cleared
- match hashed identifiers 47%
- ✓ uploaded · offline conversions attributed
Built for the teams that own the number.
Teams with conversions closing in POS, call centre, or CRM systems.
From kickoff to verified events.
-
Source
Ingest offline events from POS, CRM, warehouse, or file drop.
-
Match
Hashed email, phone, and available identifiers prepared per Snap spec.
-
Deliver
Scheduled delivery to Snap CAPI, deduped and monitored.
WHAT FLOWS WHERE
One use case, every source.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then delivers the conversion to Snap's Offline Conversions API.
A sale closes in your POS or CRM, Signals hashes the customer identifiers on a scheduled batch, matches them, then delivers the conversion to Snap's Offline Conversions API.
What ships with this offering.
Offline outcomes inside Snap campaign optimization.
Delivery cadence matched to your operational reality.
Hashed, privacy-safe identifier handling end to end.
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 :: offline payload
- > POST /v3/conversion event_conversion_type=OFFLINE
- event_type "PURCHASE" · transaction_id "pos-48112"
- hashed_email "a2c9…" · hashed_phone_number "6d41…"
- price 249.00 · currency AED
- ✓ received · pending_match
Adjacent moves on the same stack.
snap
Snap Web CAPI
Datahash is a Snapchat Marketing Partner. We deliver Snap CAPI for web, deduped with the Snap Pixel and enriched with hashed first-party identifiers.
Learn moresnap
Snap App CAPI
Server-side app conversion tracking into Snap, integrated with your MMP.
Learn more
meta
Meta Offline CAPI
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.
Learn more
tiktok
TikTok Offline eAPI
Move your in-store and call-centre conversions to TikTok server-side, so TikTok can optimize campaigns on the outcomes that matter.
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.
What offline events can be sent to Snap?
Any conversion your source systems record, most commonly in-store purchases, call-centre sales, and CRM-closed deals, mapped to Snap's event taxonomy during setup. Events are ingested from POS, CRM, warehouse, or file drop depending on where each system of record lives, then matched with hashed identifiers before delivery, so Snap can attribute outcomes that never touch a browser or app.
What delivery cadence works best?
Fresher is better for optimization, so we default to daily where your systems allow. Weekly batches also work; Snap attributes events uploaded within its lookback windows, so the campaign still gets credit for the sale even on a slower schedule. We match cadence to your operational reality, whether that is a nightly POS export or a weekly CRM pull, and monitor every delivery.
How do you match offline conversions to Snap ads?
Through hashed customer identifiers such as email and phone, prepared per Snap's spec before they ever leave your systems. Snap matches them to ad exposure on its side; raw PII never leaves your environment unhashed. The same delivery is deduped and monitored, so a single offline sale is not counted twice against the campaign it should be attributed to.
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.