Key takeaways
- The TikTok Events API (also called the TikTok CAPI) sends conversion events server-side, so they do not depend on the browser loading the pixel.
- It is designed to run with the TikTok Pixel, with a shared event ID so TikTok deduplicates the overlap.
- Customer identifiers such as email and phone are hashed before they are sent, so TikTok receives irreversible strings.
- You choose which events to send, mapping the actions that matter, such as purchase, lead, and add-to-cart.
- It can combine online and offline events, so in-store or CRM outcomes reach TikTok alongside web events.
- More complete, better-matched events give TikTok's automated delivery a fuller signal to optimise on.
- It measures conversions that happen; it cannot create demand a weak campaign failed to generate.
What is the TikTok Events API?
The TikTok Events API is TikTok’s server-side channel for conversion events. The TikTok Pixel measures actions in the browser, which is increasingly unreliable as ad blockers and cookie restrictions suppress a share of pixel events. The Events API sends the same events from your server instead, where those restrictions do not apply. The TikTok Business Help Center documents it as the server-side counterpart to the pixel, meant to run alongside it rather than replace it. Together they give TikTok two paths to the same event, so a conversion the browser drops still arrives from the server. Datahash covers the mechanics in its guide to implementing the TikTok Events API.
How does the TikTok Events API capture missing conversions?
The TikTok Events API captures conversions the pixel misses by sending them from a place the browser cannot block. When an ad blocker, a tracking-prevention setting, or a cleared cookie stops a pixel event, that conversion simply never reaches TikTok, and it cannot be attributed or optimised on. The Events API sends the event from your server, so it survives. Running both paths, with a shared event ID, means TikTok keeps one copy and discards the duplicate, so you get the browser detail the pixel captures and the reliability the server adds, without double-counting.
How do you choose which events to send to TikTok?
Choosing which events to send to TikTok means mapping the customer actions that carry business meaning, not sending everything. The TikTok Business Help Center describes a standard set of events, and the ones below are the common choices for a conversion campaign.
| Event | What it signals | When to send it |
|---|---|---|
| Complete payment | A purchase was made | At order confirmation |
| Submit form | A lead was captured | When the form is submitted or qualified |
| Add to cart | Purchase intent | When an item is added |
Send the events that map to your objective, and send them consistently from both the pixel and the server so the deduplicated record stays clean. Datahash documents setting up the TikTok Events API for web.
How do you combine online and offline event data for TikTok?
Combining online and offline event data for TikTok means sending conversions that happen away from the website alongside the web events, so TikTok sees the whole funnel. A sale closed in store or in a CRM can be sent to TikTok as an offline event, matched on hashed identifiers, so a campaign that drove an in-person purchase gets credit for it. Datahash supports TikTok app events and TikTok offline events on the same connection as web, so online and offline outcomes reach TikTok through one setup.
How do you set up the TikTok Events API?
Setting up the TikTok Events API is a short, ordered process. Run the steps in order:
- Choose the integration route: a direct server-side build, or a managed connector that handles the connection for you.
- Select the events to send and map them to your business actions.
- Normalise and hash the customer identifiers, and attach a shared event ID for deduplication with the pixel.
- Send the events to the TikTok Events API and confirm they arrive using TikTok’s test-event tools.
- Check that the pixel and server events deduplicate cleanly before you scale spend.
What are the limits of the TikTok Events API?
The TikTok Events API improves how reliably events reach TikTok; it does not create events that never happened. If a campaign does not drive conversions, there is nothing to send, and better plumbing will not fix a weak offer or creative that does not land. Match quality depends on the identifiers you attach, so events sent without an email, phone, or click ID match poorly. Running it without deduplication double-counts, which corrupts both reporting and optimisation. And Datahash has no published TikTok client outcome to quote here, so the case for it rests on the documented behaviour rather than a figure. The Events API recovers and stabilises signal that already exists. It is not a substitute for a campaign worth measuring.
What Datahash does about this
Datahash runs the TikTok Events API as managed server-side infrastructure. It hashes the identifiers, sends the web, app, and offline events, and configures deduplication against the pixel so numbers stay honest, all from one first-party data layer that also feeds Meta, Google, and Snap. Because the hashing happens before anything leaves your systems, the setup stays consistent with GDPR and DPDP. Rather than quote a TikTok client figure it does not have, Datahash grounds the setup in TikTok’s own documented matching behaviour, and shows the event delivery and match quality per connection so you can see the recovery rather than assume it. One setup carries the same identifier discipline across every platform you run.