10 minutes with a partner, a developer day without one.
Madder does not set up the Events API; it lives between your server and TikTok. What Madder does: once the connection exists, the agent sees more complete lead counts and a steadier cost per lead, and it stops flagging "leads lower than clicks suggest" on TikTok campaigns.
Before you start#
- A working TikTok Pixel with a lead event (Install the TikTok Pixel). Events API is a companion, not a replacement.
- Know where your leads are created: a Shopify order, a CRM record, a form on your own backend.
1. Decide whether you need it#
The pixel runs in the visitor's browser, and TikTok notes "connectivity issues and browser inconsistency can impact conversions reported via Pixel" — ad blockers, Safari's tracking limits, consent choices. The Events API sends the same events from your server, and TikTok recommends running both "together with Event Deduplication". Worth it when TikTok reports clearly fewer leads than your CRM, when you sell on Shopify (it is a switch), or when leads are created off-site, in a CRM or by phone.
2. Shopify: one setting#
Open the TikTok app in your Shopify admin (the same app that installed the pixel) and set data sharing to Enhanced or Maximum. That level turns on the server-side connection; TikTok's Shopify events include View Content, Add to Cart, Initiate Checkout, Add Payment Info, Complete Payment, Complete Registration, Subscribe and Search.
3. Other partners: pick one in Events Manager#
In Tools → Events Manager → Connect data source → Web (as of September 2026), choose Partner Integration and select your platform. TikTok groups them as commerce partners (Shopify, WooCommerce), data partners (customer data platforms, tag managers such as server-side Google Tag Manager, CRMs) and direct integration. The partner's own screen finishes the connection with your Pixel ID.
4. Direct integration: what to hand a developer#
Ask your developer for a "TikTok Events API 2.0 integration against the existing Pixel ID". They need an access token generated in Events Manager, and they must send the same event_id from the pixel and the server so TikTok deduplicates. The events to send are the ones from your pixel, with the customer's hashed email or phone as match keys.
5. Validate#
In Events Manager open the pixel and the Test Events tab. Server events show alongside browser events; a lead should appear once, not twice. Under Diagnostics TikTok lists deduplication and match-key problems with a suggested fix.
If it doesn't work#
- Every lead counts twice — the pixel and the server send different
event_idvalues; make them identical for the same action. - Server events show, browser events vanish — that is the pixel being blocked, exactly what the Events API is for; nothing to fix.
- Shopify shows Standard only — update the TikTok app in Shopify and re-connect the ad account.
- Low match quality in Diagnostics — the server sends no email or phone; add hashed match keys.
- Access token rejected — regenerate it in Events Manager; tokens are tied to the pixel and the ad account.