CONNECTIONS / Datahash API / Datahash API to Snap Custom Audience
Post customer segments to the Datahash API, wired to Snapchat audience matching.
Send customer segments to one documented REST endpoint from any backend, in any language; Signals matches your segments into Snapchat for targeting and customer suppression, hashed and consent-checked, with no pixel and no warehouse read.
- ● datahash-api → snap.audience :: live
- > POST /v1/events source=api.audience_members count=68,198
- hash sha256(email,phone) consent=filtered
- route snap deliver
- ✓ 202 accepted · 59,332 forwarded
WHAT THIS ENABLES
Datahash API to Snapchat Custom Audience
Datahash API to Snapchat Custom Audience: post your customer segments to one REST endpoint and Signals matches your segments into Snapchat for targeting and customer suppression, hashed and consent-checked server-side before Snapchat sees it.
- Signals matches your segments into Snapchat for targeting and customer suppression, from events your backend posts server-side.
- Snapchat audiences that stay in step as the segment rebuilds, without a pixel, a connector, or a nightly export.
WHAT FLOWS WHERE
Datahash API to Custom Audience, mapped.
Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Snapchat's Custom Audiences API records the match-ready audiences for list sizing on Snapchat.
Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then Snapchat's Custom Audiences API records the match-ready audiences for list sizing on Snapchat.
Built for the teams that own the number.
Backend and platform teams driving Snapchat audience matching by sending customer segments 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 Custom Audiences API.
-
Map
Map your event payload to Snapchat's Custom Audiences API fields once; per-request validation flags bad events instead of dropping the batch.
-
Deliver
Post events as they happen and Signals matches your segments into Snapchat for targeting and customer suppression, hashing server-side, with list sizing on Snapchat shown in the debugger.
What ships with this use case.
Snapchat audiences that stay in step as the segment rebuilds from a single server-side call.
Audiences that rebuild as the segment does, with identifiers hashed at ingestion or sent pre-hashed.
Per-event status and match feedback on list sizing on Snapchat from Snapchat's Custom Audiences API, returned inline in the live debugger.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /audience_match source=api.audience_members
- schema ["EMAIL_SHA256","PHONE_SHA256"]
- external_audience_id "aud_48708"
- id_list_size 68,198 · matched 59,332
- ✓ accepted match=87%
Adjacent moves on the same stack.
from Datahash API
Datahash API to Meta Custom Audience
Datahash API to Meta Custom Audience: post your customer segments to one REST endpoint and…
Learn morefrom Datahash API
Datahash API to Google Customer Match
Datahash API to Google Customer Match: post your customer segments to one REST endpoint and…
Learn moresame use case
ActiveCampaign to Snap Custom Audience
ActiveCampaign to Snapchat Custom Audience: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
Snap Custom Audience
Build and refresh Snap audiences from your CRM, warehouse, or SingleView with hashed…
Learn moreAsked on almost every call.
Which backends can send to Snap Custom Audience through the Datahash API?
Any backend that can make an HTTPS request. You POST customer segments as JSON to one documented endpoint and Signals forwards the match-ready audiences to Snapchat's Custom Audiences API; identifiers are hashed at ingestion or sent pre-hashed, and Snapchat advertisers building lookalikes and excluding current buyers track list sizing on Snapchat in the debugger.
How fresh are Snap Custom Audience events sent over the API?
As fresh as you post them. The API accepts events in near real time, so Snapchat audiences that stay in step as the segment rebuilds 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 list sizing on Snapchat current for the teams driving Snapchat audience matching.
NEXT STEP