TikTok Events API: how to set up server-side conversion tracking on TikTok.
TikTok Events API is the server-to-server endpoint that TikTok uses to receive conversion events directly from your server, bypassing the browser pixel. The API was built (or rebuilt) after iOS ATT (April 2021) broke pixel-based conversion tracking. Most advertisers running paid TikTok campaigns in 2026 need CAPI implemented. The standard pattern is to run the browser pixel and the server-side CAPI in parallel with event deduplication; the browser captures what the server cannot see, the server captures what the browser cannot send. Together they rebuild most of the conversion signal lost in 2021.
Key takeaways
- TikTok Events API (EAPI) is TikTok's server-to-server endpoint for conversion events. Launched 2020.
- Equivalent of Meta CAPI. Same dual-implementation pattern with Pixel + EAPI deduplication via event_id.
- iOS ATT hit TikTok harder than Meta because user base skews iOS-heavy. EAPI recovers 30-40 percent of lost signal.
- Required for TikTok's smart-performance campaigns (VBO, Smart+) to bid optimally.
- external_id (your hashed user ID) is TikTok's primary cross-device matcher.
- Use standard event names (CompleteRegistration, AddToCart, PlaceAnOrder) to keep bidding optimization working.
What TikTok Events API actually is
TikTok Events API (EAPI) is TikTok's server-to-server endpoint for conversion events. TikTok launched EAPI in 2020 as the equivalent of Meta CAPI, recognizing the same pressure on browser-based pixel tracking. The recommended setup runs the TikTok Pixel and EAPI in parallel with event deduplication via event_id, same pattern as Meta.
Why TikTok advertisers need EAPI
iOS ATT hit TikTok harder than Meta because TikTok's user base skews younger and more iOS-heavy. Pixel-only conversion tracking on TikTok typically captures 40-60 percent of actual conversions post-ATT. EAPI plus Pixel deduplication recovers most of the gap and is required for TikTok's smart-performance campaigns (VBO and Smart+ ) to bid optimally.
Setup walkthrough
- Generate a TikTok Events API access token.In TikTok Ads Manager > Events Manager > select your pixel > Settings > Get access token. Store in secure env variable.
- Set up sGTM or a custom server.TikTok provides REST endpoints and a Node.js SDK. sGTM has a community-maintained TikTok EAPI tag template.
- Map web events to TikTok event names.CompleteRegistration, AddToCart, InitiateCheckout, PlaceAnOrder. Use TikTok's standard event names for best optimization.
- Add event_id for deduplication.Both Pixel and EAPI events for the same conversion must share event_id.
- Send hashed PII.email, phone, external_id (your hashed user ID). All SHA-256 hashed.
- Validate in Events Manager.TikTok's diagnostic view shows received events, match rate, and deduplication status.
Payload format
Standard TikTok EAPI event includes event (event name), event_time (Unix timestamp), event_id (deduplication), context.user.email (hashed), context.user.phone_number (hashed), context.user.external_id (your hashed user ID), and properties.value + properties.currency for ecommerce events.
Deduplication strategy
Same pattern as Meta. Both Pixel and EAPI events must share event_id. TikTok deduplicates within a 7-day window and counts the conversion once. Without matching event_ids, the same conversion gets counted twice.
Common implementation mistakes
Three failures. Using non-standard event names that TikTok's optimization does not recognize. Missing external_id (your hashed user ID), which is TikTok's primary cross-device matcher. Forgetting to pass ttp (TikTok Pixel ID cookie) for first-party browser matching.
Quick answers
- What is TikTok Events API?
- TikTok's server-to-server conversion endpoint. Equivalent to Meta CAPI. Launched 2020.
- Do I run Pixel and EAPI together?
- Yes. Same dual-implementation pattern as Meta. Deduplicate via event_id.
- What identifiers does TikTok use?
- Hashed email and phone are the primary. external_id (your hashed user ID) is TikTok's preferred cross-device matcher. Also ttp (Pixel ID cookie) for browser matching.
- How does iOS ATT affect TikTok?
- Heavier impact than Meta because TikTok's user base skews iOS. Pixel-only match rates drop to 40-60 percent post-ATT. EAPI recovers most of the gap.
- What standard event names should I use?
- CompleteRegistration, AddToCart, InitiateCheckout, PlaceAnOrder, ViewContent. Non-standard names hurt TikTok's bidding optimization.
- How long does EAPI implementation take?
- 2-4 weeks. Slightly faster than Meta CAPI because TikTok's API is more straightforward.
Frequently asked
What is TikTok Events API (EAPI)?
TikTok's server-to-server endpoint for conversion events. Launched in 2020 as the equivalent of Meta CAPI. Sends events from your server directly to TikTok, bypassing the browser Pixel.
Why does TikTok need EAPI?
Same reason as Meta: iOS ATT, browser tracking restrictions, and ad blockers degraded the Pixel. EAPI sends events from a server where these restrictions do not apply. The signal recovery is especially valuable on TikTok because the user base skews younger and more iOS-heavy.
How is TikTok EAPI different from Meta CAPI?
Same fundamental architecture (server-to-server, runs in parallel with browser pixel, deduplicates via event_id). Different payload format, different access-token mechanism, different cross-device matching identifiers (TikTok prioritizes external_id over fbp).
What is external_id in TikTok EAPI?
Your hashed internal user ID. TikTok uses it as the primary cross-device matcher. Pass it whenever you have an authenticated user. Without external_id, TikTok falls back to email and phone matching, which is less reliable cross-device.
Should I use standard TikTok event names?
Yes. CompleteRegistration, AddToCart, InitiateCheckout, PlaceAnOrder, ViewContent. TikTok's bidding optimization is trained on these standard names. Custom event names work for tracking but hurt bidding performance.
How does deduplication work?
Both Pixel and EAPI events for the same conversion must share event_id. TikTok deduplicates within a 7-day window and counts the conversion once. Match the event_id field exactly between the two events.
What is the difference between EAPI and TikTok Pixel Helper?
Pixel Helper is a Chrome extension for debugging the browser Pixel. EAPI is the server-side API. They solve different problems — Pixel Helper helps you debug the client side, EAPI is the production server-side implementation.
How long does TikTok EAPI implementation take?
2-4 weeks for a mid-market advertiser. Slightly faster than Meta CAPI because TikTok's API surface is smaller and the integration patterns are simpler.
Sources cited on this page
- Meta — Conversions API documentation.
- Google — Google Ads Conversions API documentation.
- Apple — App Tracking Transparency framework.
- Simo Ahava — Most-cited resource on server-side GTM and CAPI.
- Real Growth Matters Inc. — Internal CAPI implementation audits, 2024-2026.