TikTok Events API + TrackPlay
TikTok optimises on what you feed it. Feed it page loads and it finds you page loaders. TrackPlay sends real orders from our server.
Attention and intent, not arrivals
TrackPlay posts to the TikTok Events API from our server. The ttclid captured when the viewer landed rides on the event, with hashed email and phone.
- A cart postback becomes CompletePayment, with value and currency
- Watch milestones and CTA clicks train the bidder
- Your own browser pixel, if you run one, is unaffected
Live in three steps
Two fields from TikTok Events Manager.
Copy your Pixel Code
From TikTok Events Manager.
Create an access token
An Events API token, in the same place.
Paste both and save
Add them in the Integrations tab.
The events TikTok receives
Sent server to server.
CompletePayment- Your cart posts the sale back
SubmitForm- A lead is captured
ClickButton- A CTA is clicked
ViewContent- At watch milestones
HotLead- Custom audience event for hot viewers
Works with the rest of your stack
Every ad platform gets the same sale. Browse all integrations
TikTok Events API questions
Does TrackPlay send conversions to TikTok?
Yes. A cart postback becomes a CompletePayment event sent server-side with value and currency.
What TikTok events does TrackPlay send?
CompletePayment on a sale, SubmitForm on a lead, ClickButton on CTA clicks, ViewContent on watch milestones, plus a custom HotLead audience event.
Do I need the TikTok browser pixel?
No. TrackPlay's delivery is server to server. If you run the browser pixel on your own pages, that is separate and unaffected.
How is the sale matched to the TikTok ad?
The ttclid captured when the viewer landed rides on the server event, together with hashed email and phone.