TikTok Custom Audience
TikTok Custom Audience sync, refreshed automatically.
Datahash syncs hashed customer audiences from your CRM, warehouse, or files to TikTok for targeting, suppression, and lookalike seeds. Segments refresh on a schedule you set, with incremental adds and removes instead of full re-uploads.
- ● tiktok.custom_audience :: live
- > sync segment "repeat_buyers_90d"
- rows 184,203 identifiers sha256(em,ph)
- tiktok.custom_audience upserted
- ✓ audience refreshed from source of truth
Built for the teams that own the number.
Teams manually re-exporting customer lists to TikTok Ads Manager.
From kickoff to verified events.
-
Connect
Connect the TikTok ad account with scoped access, then choose the segments or source records that define each audience.
-
Map
Map identifier fields in the visual mapper.
-
Deliver
Verify the first sync in the live debugger, then go live on the refresh schedule you choose.
WHAT FLOWS WHERE
One use case, every source.
A segment is defined once from your CRM, warehouse, or files, Signals hashes the identifiers and applies the rules, then syncs the audience to TikTok and keeps it refreshed on a schedule.
A segment is defined once from your CRM, warehouse, or files, Signals hashes the identifiers and applies the rules, then syncs the audience to TikTok and keeps it refreshed on a schedule.
What ships with this offering.
Audience segments synced to TikTok on a schedule you control.
Incremental adds and removes, so lists stay current without full re-uploads.
One segment definition that can fan out to every connected audience destination.
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 :: audience payload
- > POST /open_api/v1.3/segment/mapping/ action=append
- id_schema [EMAIL_SHA256, PHONE_SHA256, IDFA_SHA256]
- hashed_email "c4d9…" · hashed_phone "2a71…"
- rows 184,203 · op upsert
- ✓ code 0 · audience updated
Bring 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 often do TikTok Custom Audiences refresh?
On the schedule you choose, typically daily. Datahash sends incremental additions and removals on each refresh, so the audience stays current without re-uploading the full list every time, and records that fail to match are flagged instead of silently dropped.
Is customer PII stored to run TikTok Custom Audience sync?
No. Identifiers are hashed with SHA-256 before any list reaches TikTok, and no PII is stored on host servers in Datahash Cloud. A self-hosted Core deployment is available if audience data cannot leave your own environment, and the same hashing rule applies to every source you connect.
Can the same audience segment feed TikTok and other platforms?
Yes. A segment defined once in Datahash can sync to TikTok, Meta, Google, and Snapchat at the same time, each with its own identifier mapping and delivery status, so marketing does not rebuild the same segment logic for every ad platform.
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.