ttclid
TikTok Click Identifier
How it works
After a click on a TikTok ad, the landing page opens with ?ttclid=... in the URL. The TikTok pixel reads the value and also sets the _ttp cookie, an identifier for the browser. Through the Events API you send conversions from your server, with the ttclid, _ttp and hashed contact data. That tells TikTok which user and which click an event belongs to.
Why it matters
The pixel alone misses conversions: when consent is missing, an ad blocker steps in, or the deal happens later in the CRM. When the event comes from the server, TikTok often has no link to the click without the ttclid. The more conversions TikTok can match, the better its delivery learns which users convert. TSO stores the ttclid with the visit and sends the person's latest TikTok click, along with _ttp, through the Events API with every conversion.
Example
An online course provider promotes a webinar. In one week, TikTok ads bring 60 sign-ups. 45 of them happen right after the click on a phone and carry the ttclid. 15 people sign up later on a laptop: there is no ttclid there, so TikTok can only match them through the hashed email, if it belongs to a TikTok account.
Common mistakes
- Using only the pixel: without server events, conversions that never reach the browser are missing.
- Losing the ttclid on a domain change: if the form lives on another domain, the click ID has to travel with the visitor.
- Pixel and server without a shared event ID: TikTok then counts the same sign-up twice.