TikTok Segment (Streaming)
Stream audience membership to TikTok in near-real-time via the Segment API — each member is mapped into (or out of) a TikTok segment individually as they qualify or drop out. This is the low-latency alternative to the file-based TikTok Ads Custom Audience destination.
Use this when membership changes fast and freshness matters — e.g. adding a cart-abandoner within minutes, or promptly removing a user who withdrew consent.
Prerequisites
- A TikTok Business Center account and Advertiser ID.
- The TikTok Segment / Streaming partner permission on the connecting app. Unlike the self-serve Custom Audience API, the Segment API is permission-gated by TikTok — the app must be allowlisted for it.
- An existing TikTok segment (audience) ID to map members into.
Authentication
TikTok Segment uses OAuth 2.0 via TikTok Business Center — the same flow as TikTok Ads.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Advertiser ID | Text | Yes | Your TikTok Ads advertiser ID (numeric). |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Segment / Audience ID | Text | Yes | The TikTok segment (audience) ID members are mapped into. |
| Identifier Type | Select | Yes | The identifier streamed per member, matching the mapped column: EMAIL_SHA256 → Email, PHONE_SHA256 → Phone, IDFA → iOS MAID, AAID → Android MAID. All SHA-256 hashed (MAIDs uppercased). |
Supported Operations
Audience Sync Modes: Add, Remove, Mirror
Membership is streamed incrementally: entering the audience sends action=add, exiting sends action=delete. Mirror mode maps both automatically off the sync diff.
Features
- Field Mapping: No
- Schema Introspection: No
Match Keys
| Field | Type | Description |
|---|---|---|
email | string | Raw email — lowercased, trimmed, SHA-256 hashed. Use with EMAIL_SHA256. |
hashed_email | string | Pre-hashed SHA-256 hex of the email. |
phone | string | Raw phone — normalized to E.164, SHA-256 hashed. Use with PHONE_SHA256. |
hashed_phone | string | Pre-hashed SHA-256 hex of the E.164 phone. |
maid | string | Device advertising ID — uppercased and SHA-256 hashed. Use with IDFA (iOS) or AAID (Android). |
hashed_maid | string | Pre-hashed SHA-256 hex of the uppercased MAID. |
How it works
For each batch, members entering the audience are sent to segment/mapping/ with action=add and those leaving with action=delete, in requests of up to 1,000 members. Each record carries the identifier, its id_type, and the target audience_ids. Unlike a file upload, there is no staging step — mappings apply in near-real-time.
Custom Audience vs Segment (Streaming)
| Custom Audience (TikTok Ads) | Segment (this destination) | |
|---|---|---|
| Delivery | Batch file upload, full refresh | Inline, near-real-time add/remove |
| Latency | ~1 hour to activate | Near-real-time |
| Permission | Self-serve | Partner-gated (allowlist) |
| Best for | Scheduled audience refreshes | Fast-moving audiences, prompt suppression |
Troubleshooting
Permission / not authorized for the Segment API
The Segment/Streaming API is allowlisted by TikTok. If calls fail with a permission error, the connecting app has not been granted Segment access — contact your TikTok partner representative.
Segment ID not found
Verify the Segment / Audience ID exists under the configured advertiser in TikTok.