Amperity and TikTok Ads: TikTok Events API and audiences
Send customer audiences from Amperity through the TikTok Ads Segment API and eligible offline or web events through the TikTok Events API, with separate configurations for audience delivery and conversion measurement.
Get a demoSee the TikTok Ads docsCustom Audiences • Events API • One-time audience deliveries

Use customer audiences and events in TikTok Ads
Reach repeat-purchase audiences selected from available customer history.
Prepare customer audiences as seeds for eligible TikTok lookalike modeling.
Reconnect with customers selected by purchase recency or loyalty criteria.
Use customer-defined exclusions where the campaign supports them.
Supply eligible store transactions for TikTok conversion reporting.
Send supported web purchase events through the separately configured event path.
How Amperity connects to TikTok Ads
Select the audience or events. Define customer membership with a segment, or use a query for the supported event payload.
Configure the matching path. Use the Segment API destination for audiences and the Events API destination for offline or web events.
Validate the receiving object. Check the audience or event source in TikTok before planning the next audience delivery or event orchestration.
Audience delivery and conversion delivery use separate configurations.
Match customers using the supported identity fields
TikTok audiences support configured email, phone, Android advertising ID and Apple IDFA inputs. Amperity hashes EMAIL, PHONE and AAID automatically; IDFA is sent unhashed. A usable Custom Audience requires at least 1,000 matched TikTok users, so uploaded row count alone does not establish activation eligibility.
What the TikTok Ads connection supports
Capability | Supported behavior |
|---|---|
Audience route | TikTok Ads Segment API; refreshing requires a new one-time segment delivery. |
Audience identity | EMAIL, PHONE, AAID or IDFA, as configured; IDFA differs from the hashed inputs. |
Audience eligibility | At least 1,000 matched users before use in an ad group. |
Events route | Separate TikTok Events API destination for offline or web events and an existing event source. |
Timing | Connector audience mapping can take up to 10 hours after sending; events have separate processing. |
Authentication | TikTok OAuth and advertiser ID; Operator or Admin account permission, not Analyst. |
Use TikTok audiences for retention and acquisition
Use a customer audience for repeat-purchase outreach
Build a customer segment from purchase recency, available category history, or loyalty information in Amperity. Deliver its supported identifiers to TikTok and inspect the matched audience before using it in an ad group. Your media team chooses the creative and campaign settings. Plan each later refresh as a new one-time delivery rather than assuming the audience stays synchronized automatically.
Prepare a seed for lookalike modeling
Select an audience that represents the customers your acquisition strategy aims to reach, using the customer context available in Amperity. Deliver eligible identifiers, then use the Custom Audience within TikTok for supported lookalike modeling. TikTok performs the modeling and controls its eligibility requirements. A well-defined Amperity seed does not guarantee an audience size, reach level, or campaign-performance improvement.
Include store activity in conversion reporting
Select recent offline transactions and map the required identity, timestamp and event fields to the separate Events API destination. Use the offline event source ID rather than a web Pixel ID for this path. After delivery, inspect events and reporting in TikTok. The resulting signals support platform measurement; they do not establish that advertising caused every reported purchase or provide universal cross-channel attribution.
Set up and validate the connection
Ask your Datagrid Operator or Amperity representative to configure the advertiser ID and OAuth access with an Operator or Admin account. Validate supported identity fields and the matched audience size before use; new one-time deliveries are required for later audience refreshes.
For event delivery, configure an existing offline event set or web pixel, the matching event-source ID and event fields. Current Amperity guidance accepts events from the previous 28 days; attribution windows and processing remain distinct. Inspect a sample in TikTok before scheduling event orchestrations.
Audience setup docsConversion setup docsTikTok Ads integration FAQs
Does Amperity send both TikTok audiences and events?
How many customers must match before I can use a Custom Audience?
Does TikTok audience membership refresh automatically?
How long do TikTok audience updates take?
Can I send the same query for offline and web events?
Keep TikTok customer audiences and conversion signals grounded in your data
Explore the audience and event workflows that fit your campaign needs.
Get a demo