TikTok

TikTok

TikTok Events API v1.3 with automatic ttclid capture, ttp propagation, and server-side event delivery through TrackLayer.

This guide covers the shortest path from a TikTok pixel in Ads Manager to validated server-side events in TrackLayer. The objective is to confirm that TrackLayer receives your event once, preserves TikTok click and browser identifiers, and sends a valid Events API request without forcing you to maintain the payload yourself.

Setup

1. Open TikTok Ads Manager, then go to Assets → Events or Events Manager for the ad account you are using. Copy the Pixel Code and generate an Access Token for the Events API integration. Make sure the token belongs to a user or business role that still has access to the ad account.

2. In TrackLayer, open Platforms and connect TikTok. Paste the Pixel Code and Access Token into the connector form. Save the platform before sending any test traffic so TrackLayer can validate the credentials first.

3. Fire a test event from a real browser session. A PageView, AddToCart, or CompletePayment event is fine. Use a landing page that includes TikTok click data when possible so ttclid is available. If your site sets the TikTok browser cookie, TrackLayer will also pick up ttp.

4. Open the TikTok Test Events console for that pixel and confirm the event arrives through the Events API. Check that the event name, timestamp, and key identifiers match what you expected from the source event.

5. After validation, decide whether the browser pixel should stay active. If you still need it for browser-side TikTok features, leave it in place and use a stable event_id strategy. If you want a server-only setup, remove the redundant browser event path after testing.

How the event flows

Browser / app
  -> TrackLayer /ingest
  -> normalize + restore ttclid / ttp
  -> server-side TikTok Events API v1.3 call
  -> TikTok

TrackLayer takes the event payload you already send and turns it into the request TikTok expects. You do not need a separate TikTok-specific implementation path for basic purchase and funnel events.

What we handle for you

TrackLayer covers the pieces that usually create drift between browser and server reporting:

• stable event_id handling so client and server events can be reconciled cleanly
• ttclid capture from landing-page parameters when the ad click reaches your site
• ttp cookie propagation when the browser has already set it
• payload maintenance for Events API v1.3 so version changes do not become an app-side rewrite

That lets you keep your source schema consistent while TrackLayer owns the TikTok delivery format.

Data to send

For TikTok, click identifiers matter. Preserve ttclid across redirects, checkout hops, and custom landing pages. If your frontend strips it before the purchase completes, attribution quality drops quickly. Keep the ttp cookie intact as well; it helps TikTok connect browser sessions to the server event.

You should also send the usual conversion context: event name, timestamp, value, currency, order or transaction ID, and user identifiers when available. Email and phone should be normalized before TrackLayer receives them. If the event is created on your server, pass through the original IP and user agent when policy allows. TikTok accepts leaner payloads, but match quality and campaign reporting improve when browser context is preserved.

Troubleshooting

No events in Test Events

First confirm the Pixel Code in TrackLayer matches the pixel you are inspecting in TikTok Events Manager. Then verify the Access Token is still active. If both are correct, check that the source event actually reached TrackLayer before debugging TikTok delivery.

Low match quality

This usually means ttclid, ttp, IP, user agent, email, or phone are missing. The most common failure is losing ttclid during redirects, especially when users land on one domain and convert on another. Fix the parameter propagation first.

Test Events console link mismatch

Teams often validate in the wrong ad account or wrong pixel workspace. Open the Test Events console from the same pixel record that supplied the Pixel Code. If you bookmark the page, re-check the account switcher before assuming the event failed.

Once TikTok Test Events looks clean, send normal traffic and monitor rejection rates, click-ID coverage, and event-name mapping during the first production day.

-> Back to all platforms