Webclat / Signals
Signals  /  CAPI  /  TikTok Events API Implementation

TikTok Events API Implementation

Server-side event delivery for TikTok Ads: how it works, dedupe with the Pixel, consent handling, the Shopify path, and how to verify delivery in Events Manager.

Quick answer

TikTok Events API sends conversion events from your server directly to TikTok, deduplicated against the TikTok Pixel by a shared event ID, recovering conversions the browser-only Pixel would otherwise lose to blockers and tracking prevention.

What TikTok Events API does

TikTok's Events API sends conversion and engagement events (ViewContent, AddToCart, CompletePayment, and others) from your server to TikTok directly, the same events your TikTok Pixel already tracks client-side. It exists for the same reason Meta's Conversions API exists: pixel-only delivery loses events to browser and network conditions the server does not depend on.

How delivery works

A server-side HTTP POST to TikTok's Events API endpoint carries the event name, timestamp, matched customer parameters (hashed email/phone where available), and an event ID shared with the corresponding client-side Pixel event for the same action.

  • Server-side GTM. If a server-side Google Tag Manager container is already in place, TikTok Events API becomes another tag reading from the same event stream.
  • Shopify. TikTok's Shopify channel app includes native server-side event delivery - the fastest path for Shopify merchants.
  • Direct integration. A backend call from your application server for custom platforms.

Dedupe with the TikTok Pixel

Send the same event ID from both the Pixel and the Events API call for the same real-world action. Without it, TikTok either double-counts the conversion or reports the server event as unmatched to any browser signal - neither is correct, and both muddy optimization decisions TikTok's algorithm makes off this data.

Consent handling

Gate the server-side event on the same consent record your Pixel implementation respects. A visitor who declined tracking consent should not generate a server-side event any more than a client-side one.

How to verify it worked

  1. Open TikTok Ads Manager -> Assets -> Events, and check the connection status and delivery health for your Events API source
  2. Use TikTok's Test Events tool to confirm a sent event registers with the correct parameters
  3. Confirm match rate is reported and reasonable - a very low match rate usually means missing or improperly formatted hashed customer data, not a broken connection
  4. Fire a real or controlled test conversion and confirm it appears once, not duplicated across Pixel and server sources

Frequently Asked Questions

What is the TikTok Events API?

The TikTok Events API is a server-to-server connection that sends conversion and engagement events from your server directly to TikTok, complementing the browser-based TikTok Pixel. It is TikTok's equivalent of Meta's Conversions API - built for the same reason, browser-side event loss.

Does TikTok Events API need to run alongside the Pixel?

Yes. Send both, deduplicated with a shared event ID, the same pattern as Meta CAPI. TikTok's documentation calls this hybrid approach the recommended setup, not an either/or choice.

Is there a Shopify integration for TikTok Events API?

Yes. TikTok's Shopify app supports server-side event delivery natively, which is the fastest path for Shopify stores. Custom platforms need a direct server integration or a server-side GTM tag.

How do I verify TikTok Events API is working?

In TikTok Ads Manager, under Events Manager for your Pixel/Events source, check event delivery status and match rate per event, and use TikTok's test event tool to confirm a server-tagged event registers correctly before relying on live traffic.

Running TikTok Ads Without A Server-Side Events Connection?

We will check your current TikTok Pixel setup and tell you what a server-side Events API implementation would recover.

Talk To The Practice