How Do You Track Conversions on TikTok Ads?

You track conversions on TikTok Ads by combining the browser-based TikTok Pixel with the server-side Events API, linked by a matching event_id so the same action isn't counted twice. TikTok positions both as required layers of a complete setup in 2026 — the Pixel captures browser-side signal and the ttclid attribution anchor, while the Events API sends enriched, server-verified event data the browser alone can't transmit.

The TikTok Pixel: Your Starting Point

The Pixel is a base code snippet placed on every page of your site, plus individual event tags for specific actions you want to optimize toward — typically CompletePayment or Lead. It's created inside TikTok Ads Manager under Events Manager, where you set up a web data source and choose an installation method: a partner integration, Google Tag Manager, or manual code placement. Like any browser-based pixel, its signal degrades under ad blockers and browser privacy restrictions — industry guidance puts the share of Pixel events blocked before reaching TikTok as high as 35% in 2026.

The Events API: Server-to-Server Recovery

The Events API closes that gap by sending conversion data directly from your server rather than the visitor's browser. For a custom-built site, your server sends an HTTP POST request to TikTok's event tracking endpoint, carrying your pixel ID, an access token, and enriched customer identifiers the browser can't reliably pass along, such as hashed email or phone match data.

Setup Steps

Create or select a web data source. In TikTok Ads Manager, open Events Manager and add a new web pixel tied to your domain.

Install the base Pixel code. Use TikTok's Google Tag Manager template, a partner integration, or manual placement in your site's header.

Generate an Events API access token. Inside the same data source, set up server-side event delivery and generate the token your server will use to authenticate.

Send matching events from both sources. Fire the same conversion — purchase, lead, signup — from the Pixel and again from your server, carrying an identical event_id on both.

Why Deduplication Matters Here Too

Without a matching event_id, TikTok has no way to tell that a Pixel-reported purchase and a server-reported purchase are the same conversion, so it counts both — inflating reported volume and understating real cost per action. TikTok's own guidance calls deduplication a required step whenever Pixel and Events API run together, using the shared event_id as the matching key.

Bottom Line

Install the Pixel first if you're starting from nothing, then layer the Events API on top of the same events rather than treating it as a separate tracking system, and verify every event carries a matching event_id before trusting the combined conversion count. If you're relying on a partner platform — Shopify, a CRM, a tag manager — check whether it already supports TikTok's Events API natively before building custom server code; most major ecommerce platforms do, which removes the development step entirely.

Sources: TikTok for Business Help Center's Events API and Pixel setup articles; implementation detail from Benly, The Ad Spend, and Stackmatix's 2026 coverage of TikTok conversion tracking.