How Do You Set Up the TikTok Events API for Conversion Tracking?

TikTok conversion tracking works through two connected pieces run together: the browser-based TikTok Pixel, installed as base code on every page, and the server-side Events API, which sends the same events directly from an advertiser's server and is deduplicated against the Pixel using a shared event ID.

Setting up the TikTok Pixel first

Under Assets, then Events, then Web Events in TikTok Ads Manager, create a new pixel and choose an install method — manual code, a partner integration, or Google Tag Manager. Deploy the base code site-wide, then configure the standard events relevant to the business: ViewContent, AddToCart, InitiateCheckout, and CompletePayment for e-commerce, or Lead for a lead-generation form submission. TikTok's own Pixel Helper browser extension verifies the pixel fires correctly on a live page — a green checkmark confirms it's working.

Adding the Events API on top

Once the Pixel is live, the Events API is configured from the same pixel: Assets, then Events, then Web Events, select the pixel, and choose Set Up Events API. That generates an access token used to authenticate server-to-server calls sent to TikTok's Events API endpoint. TikTok explicitly recommends implementing the Events API alongside an existing Pixel integration rather than as a replacement for it, framing it as a way to maximize measurement performance rather than an alternative setup path.

What the server-side payload needs to include

Each event sent through the Events API needs an event_name, a timestamp, the pixel_code, an event_id, a properties object carrying details like value and currency, and a user_data object carrying hashed personally identifiable information used for matching. That event_id is the field that ties a server-side event back to its browser-side counterpart.

Why deduplication matters

Because the browser Pixel and the server-side Events API can both fire for the same real-world action — a completed purchase, for instance — TikTok deduplicates them using that matching event_id, so a single conversion doesn't get counted, and potentially double-attributed, twice. Sending events from both sources without matching event_ids is the most common way this setup goes wrong, inflating reported conversion volume rather than filling in gaps the Pixel alone would have missed.

Why run both instead of just one

The Pixel captures real-time browser-side behavior directly, but browser-level tracking is affected by ad blockers, cookie restrictions, and users who don't complete a page load before converting. The Events API is not subject to those browser-side limits since it sends data server-to-server, which is why TikTok positions the two as complementary layers rather than either one being sufficient on its own.

Verifying the full setup

Under Assets, then Events, confirm the pixel shows an Active status with recent event data flowing in, and check that events originating from the Events API appear alongside Pixel-sourced events rather than as a separate, disconnected stream.

Bottom Line

Install the TikTok Pixel first and confirm it fires with Pixel Helper, then layer the Events API on top of the same pixel using a shared event_id for deduplication — treat the two as one tracking system running in parallel, not two separate setups to choose between.