CONNECTIONS / Datahash API / Datahash API to TikTok Custom Audience
Post customer segments to the Datahash API, wired to TikTok audience targeting.
Send customer segments to one documented REST endpoint from any backend, in any language; Signals delivers first-party segments to TikTok as match-ready custom audiences, hashed and consent-checked, with no pixel and no warehouse read.
- ● datahash-api → tiktok.audience :: live
- > POST /v1/events source=api.audience_members count=16,123
- hash sha256(email,phone) consent=filtered
- route tiktok deliver
- ✓ 202 accepted · 12,415 forwarded
WHAT THIS ENABLES
Datahash API to TikTok Custom Audience
Datahash API to TikTok Custom Audience: post your customer segments to one REST endpoint and Signals delivers first-party segments to TikTok as match-ready custom audiences, hashed and consent-checked server-side before TikTok sees it.
- Signals delivers first-party segments to TikTok as match-ready custom audiences, from events your backend posts server-side.
- TikTok custom audiences mirroring the segment your data team publishes, 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 TikTok's Custom Audience API records the match-ready audiences for match quality on TikTok.
Your backend posts each event to the Datahash API, which hashes and consent-screens it server-side, then TikTok's Custom Audience API records the match-ready audiences for match quality on TikTok.
Built for the teams that own the number.
Backend and platform teams driving TikTok audience targeting 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 TikTok's Custom Audience API.
-
Map
Map your event payload to TikTok's Custom Audience API fields once; per-request validation flags bad events instead of dropping the batch.
-
Deliver
Post events as they happen and Signals delivers first-party segments to TikTok as match-ready custom audiences, hashing server-side, with match quality on TikTok shown in the debugger.
What ships with this use case.
TikTok custom audiences mirroring the segment your data team publishes from a single server-side call.
Targeting that mirrors your live segment, with identifiers hashed at ingestion or sent pre-hashed.
Per-event status and match feedback on match quality on TikTok from TikTok's Custom Audience API, returned inline in the live debugger.
What Custom Audience actually receives.
- ● signals :: audience upload
- > POST /dmp/custom_audience source=api.audience_members
- id_schema ["EMAIL_SHA256","PHONE_SHA256"]
- action "add" · audience_id "aud_69942"
- id_list_size 16,123 · matched 12,415
- ✓ accepted match=77%
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 TikTok Custom Audience
ActiveCampaign to TikTok Custom Audience: Signals reads your ActiveCampaign contacts and…
Learn moregeneric
TikTok Custom Audience
Datahash syncs hashed customer audiences from your CRM, warehouse, or files to TikTok for…
Learn moreAsked on almost every call.
Which backends can send to TikTok 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 TikTok's Custom Audience API; identifiers are hashed at ingestion or sent pre-hashed, and TikTok advertisers seeding lookalikes and suppressing existing customers track match quality on TikTok in the debugger.
How fresh are TikTok Custom Audience events sent over the API?
As fresh as you post them. The API accepts events in near real time, so TikTok custom audiences mirroring the segment your data team publishes reaches TikTok moments after your backend fires the call, with per-event status returned inline. There is no batch window and no scheduled read, which keeps match quality on TikTok current for the teams driving TikTok audience targeting.
NEXT STEP