Send TikTok Events API events with Pixel Activator
event_idRelated: TikTok server-side GTM setup, Meta credential setup, and event deduplication.
What are TikTok Events API events?
Server delivery complements the TikTok Pixel. A vague conversion rule or ignored consent and data-handling obligations still make the event unsuitable.
Where are the Pixel Code and access token?
- Open TikTok Ads Manager and go to Tools > Events Manager.
- Select the web pixel used for the campaign and copy its Pixel Code.
- Open the pixel settings and find the Events API section.
- Generate an access token, copy it immediately, and save it in a secret store.
The existing TikTok server-side setup guide covers this route in more detail.
Which TikTok event should you select?
| Conversion action | Typical TikTok event | Do not use it for |
|---|---|---|
| Paid order | Purchase or CompletePayment | A visit to checkout |
| Lead form submitted | SubmitForm | A form view |
| Registration completed | CompleteRegistration | A registration button click |
| Product added | AddToCart | A product page view |
In TikTok Events API v1.3, Purchase is the primary recommended standard, while CompletePayment remains supported as a classic pixel web event. Pixel Activator provides both events in its UI, sending each with a test value of 1 USD. Keep a written mapping between your business actions and event names to prevent accidental changes when connecting new tools later.
How do you test the server event?
- Add the Pixel Code and token in Pixel Activator.
- Select one event linked to a real test action.
- Send it once.
- Open the selected pixel in Events Manager and use its testing or activity view.
- Check the event source, name, timestamp, and diagnostics.
For one-off event verification with TikTok, use the free Pixel Activator — it sends test events in a few clicks. For resilient automated conversion delivery with deduplication and parameter mapping, use Most.
How does TikTok deduplication work?
Generate one ID when the conversion happens and preserve it across browser and server delivery. Do not use a fixed ID for every conversion. The deduplication guide explains why stable per-event IDs matter.
Which data should you review before going live?
- Pixel Code belongs to the correct ad account and site.
- Token has not been exposed or rotated.
- Event name matches the completed business action.
- Browser and server paths use the same event ID if both operate.
- TikTok Events Manager shows the expected server event.
Common TikTok Events API mistakes
| Mistake | Symptom | Fix |
|---|---|---|
| Wrong Pixel Code | Event is missing from the expected asset | Copy the code from the selected Events Manager pixel |
| Token exposed | Security risk | Rotate the token and update the protected field |
| Same conversion sent twice | Counts do not match reality | Use one event ID and event name across both sources |
| Event chosen too early | Optimisation learns from the wrong action | Map it to the completed milestone |
What should you automate later?
Sources
Sources
- Manual testing and validation: use Pixel Activator for free test event dispatch and parameter checks before campaign launch.
- Automated routing and delivery: connect Most for resilient server-side conversion delivery with deduplication, retry queues, and pre-built integrations.