Skip to main
← Index

Connect TikTok Events API

Send your server-side events to the TikTok Events API with a Pixel ID + access token, event_id deduplication included.

Walityk sends your events to the TikTok Events API (v1.3), server-side, with an event_id per event for deduplication against the TikTok browser pixel.

Takes 5 minutes.

Prerequisites

  • A TikTok Ads Manager account with a Web pixel created.

1. Get the Pixel ID and Access Token

  1. TikTok Ads Manager → Tools → Events → Web Events → select your pixel.
  2. The Pixel ID (C4XXXXXXXXXXXXXXXX format) is shown in the pixel details.
  3. Pixel Settings tab → Generate Access Token (Events API). Copy the token.

2. Configure the destination

  1. Walityk dashboard → Destinations → your site → TikTok Events API card.
  2. Paste the Pixel ID and Access Token.
  3. Optional: a Test Event Code to view events in the Events Manager debug view without polluting stats. Remove it after testing.
  4. Save.

3. Deduplication with the browser pixel

  • If Walityk “Pixel deduplication” is enabled on the site, the tag initializes the TikTok pixel (ttq) and re-fires each browser event with the same event_id as the server copy. Remove your manual ttq.track(…) calls to avoid double counting.
  • Without a browser pixel, the Events API alone works perfectly well.

4. Verify

  1. Destinations → your site → TikTok: delivery log (each hit with its HTTP status).
  2. On the TikTok side: Events Manager → your pixel → events arrive with the “Server” channel.

Common errors

  • HTTP 401/403: invalid or expired token → regenerate it in the pixel settings.
  • HTTP 400: wrong Pixel ID (check the C4… format — it’s not the ad account ID).
  • “Skipped” events in the log = advertising consent declined. Normal.

Next steps

Need help? hi@walityk.com.