CONNECTIONS / Datahash API / Datahash API to Snap Offline CAPI
Post offline and in-store sales to the Datahash API, wired to Snapchat in-store conversions.
Send offline and in-store sales to one documented REST endpoint from any backend, in any language; Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked, with no pixel and no warehouse read.
- ● datahash-api → snap.capi :: live
- > POST /v1/events source=api.purchase_events count=25,079
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ 202 accepted · 20,816 forwarded
WHAT THIS ENABLES
Datahash API to Snapchat Offline CAPI
Datahash API to Snapchat Offline CAPI: post your offline and in-store sales to one REST endpoint and Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, hashed and consent-checked server-side before Snapchat sees it.
- Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, from events your backend posts server-side.
- Physical-world sales counted inside Snapchat performance, without a pixel, a connector, or a nightly export.
The click, the conversion, and the credit.
The conversion happens off Snap, away from any pixel. Here is how Datahash API closes the loop.
Built for the teams that own the number.
Backend and platform teams driving Snapchat in-store conversions by sending offline and in-store sales straight from their own stack.
From kickoff to verified events.
-
Connect
Create an API key in the Signals console and point your backend at the endpoint that feeds Snapchat's Conversions API.
-
Map
Map your event payload to Snapchat's Conversions API fields once; per-request validation flags bad events instead of dropping the batch.
-
Deliver
Post events as they happen and Signals reports in-store purchases against the Snapchat campaigns that reached the buyer, hashing server-side, with offline event timing shown 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 Datahash API records the event. |
What Offline CAPI actually receives.
- ● signals :: event payload
- > POST /v2/conversion source=api.purchase_events
- event_type "PURCHASE" · event_conversion_type "OFFLINE"
- hashed_email "5d8b22…" · hashed_phone_number "a179fe…"
- timestamp 1784181009 · price 13626 · currency USD
- ✓ accepted · match=true
Adjacent moves on the same stack.
from Datahash API
Datahash API to Google OCI
Datahash API to Google Offline Conversions: post your offline and in-store sales to one…
Learn morefrom Datahash API
Datahash API to Google Store Sales
Datahash API to Google Store Sales: post your offline and in-store sales to one REST…
Learn more
same use case
ActiveCampaign to Snap Offline CAPI
ActiveCampaign to Snapchat Offline CAPI: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Offline CAPI
Deliver offline conversions to Snap on a schedule that fits your operations.
Learn moreAsked on almost every call.
Which backends can send to Snap Offline CAPI through the Datahash API?
Any backend that can make an HTTPS request. You POST offline and in-store sales as JSON to one documented endpoint and Signals forwards the offline conversions to Snapchat's Conversions API; identifiers are hashed at ingestion or sent pre-hashed, and retail and QSR advertisers whose Snapchat audience buys in person track offline event timing in the debugger.
How fresh are Snap Offline CAPI events sent over the API?
As fresh as you post them. The API accepts events in near real time, so physical-world sales counted inside Snapchat performance reaches Snapchat moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps offline event timing current for the teams driving Snapchat in-store conversions.
NEXT STEP