TikTok Events API
Updated July 2026 · 1 min read
Send TikTok events from your server container with an access token from TikTok Events Manager, deduplicated against the browser pixel.
How it fits together
Your TikTok pixel keeps firing in the browser, and your server container sends the same events to the TikTok Events API from your TagVolt domain. TikTok merges both streams using a shared event ID. The tag is configured in Google Tag Manager's server container — TagVolt hosts and serves that container.
Before you start
- GA4 events flowing through your container — the TikTok tag reuses them. See Send GA4 events server-side.
- Access to your pixel in TikTok Events Manager.
Get your access token
- In TikTok Events Manager, open your pixel's settings.
- In the Events API section, click Generate Access Token and copy it.
Add the tag in the server container
- In your server container, add the TikTok Events API tag template from the Community Template Gallery (published by TikTok).
- Enter your Pixel Code and paste the access token.
- Set the tag to fire on events claimed by the GA4 client, and map your event names to TikTok's — for example, purchase becomes CompletePayment.
- Publish the server container.
Deduplicate with the pixel
When a browser pixel event and a server event share the same event_id, TikTok keeps one and discards the other. Send an event ID with the pixel and forward the same value in the server tag.
Test events in TikTok Events Manager show whether each event arrived from the browser, the server, or both — a quick way to confirm dedup works.
Verify
Fire a few test events with Preview and debug mode open and watch them land in TikTok Events Manager. Missing events? See Events not showing up.