Set up TikTok Events API (Web) as a redundant server-side channel alongside the TikTok Pixel
domain: business-api.tiktok.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In TikTok Ads Manager, go to Assets > Web Events, open the Pixel, and generate an Events API access token from Settings.
Copy the Pixel ID from the Pixel's Settings tab, needed alongside the access token for every event call.
From your server, POST event payloads to https://business-api.tiktok.com/open_api/v1.3/event/track/, including the pixel_id, access token, and an event array.
Assign the same event_id to a client-side Pixel event and its server-side Events API counterpart so TikTok deduplicates the pair instead of double-counting.
Use the Test Event Code from the Pixel's Test Events tab to validate delivery in Ads Manager before going live.
Known gotchas
Events API is meant to run as a second channel alongside the Pixel, not a replacement — turning off the Pixel loses browser-side signals CAPI can't fully replicate.
Mismatched event_id values between the Pixel and server-side calls break deduplication and inflate reported conversions.
The access token is scoped to a specific Pixel; rotating or regenerating it in Ads Manager invalidates any server integration still using the old token.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?