ttclid (TikTok Click ID) is the parameter TikTok appends to a landing page URL when someone clicks a TikTok ad. When you send web events through the TikTok Pixel or the Events API, TikTok uses the Click ID to match those events to the ad, and uses the match for attribution, audience building, ad delivery optimization and measurement (TikTok Ads Manager help).
How ttclid reaches your landing page
TikTok’s own example shows the parameter added after any query string you already use:
http://demo.mywebsite.com?a=b
http://demo.mywebsite.com?a=b&ttclid=_CLICKID_
_CLICKID_ stands in for the real value. Auto-attachment leaves your other tracking parameters alone, and TikTok describes the Click ID as a unique identifier appended every time a person clicks a TikTok ad (matching events guide).
TikTok’s help pages don’t describe the format of the value, so treat it as an opaque string and store it exactly as it arrived. You’ll see it in the landing page URL, in your server logs and anywhere your landing page copies URL parameters, such as a hidden form field. The capture pattern is the same one used for Facebook URL parameters.
Where ttclid sits among TikTok’s match keys
The same matching guide lists what TikTok uses to connect your events to its users:
| Match key | What it is |
|---|---|
Click ID (ttclid) | one value per ad click, read from the landing page URL |
ttp cookie | identifiers saved in a first-party cookie limited to your domain |
| Email and phone | Advanced Matching, hashing required |
| External ID | your own customer or cookie ID, hashing required |
| IP address and user agent | shared by default by the Pixel, configured by hand for the Events API |
The ttclid is the only key on that list that points at a specific click. The others identify a person or a browser.
How long a ttclid counts
TikTok ties it to your attribution settings: each Click ID “adheres to the same CTA window configured in Attribution Manager”, CTA being click-through attribution (TikTok). So its practical lifetime is the click-through window you configure there. A conversion that arrives after that window won’t be credited to the click, whatever value you send.
For Meta campaigns, DropCPL keeps its own click ID for every ad click. Each lead is joined to that click_id, and the fbclid travels back to Meta inside the Lead event. Start free →
ttclid vs fbclid: the same pattern
| ttclid | fbclid | |
|---|---|---|
| Added by | TikTok, on an ad click | Meta, on an ad click |
| Browser-side tag | TikTok Pixel | Meta Pixel |
| Server-side channel | Events API | Conversions API |
| Pixel and server together | TikTok recommends both, with event deduplication | Meta deduplicates on matching event ID and event name |
TikTok’s Events API overview recommends running the Pixel and the Events API together with event deduplication. Meta does the same job by matching event_id and event name between Pixel and server events received within 48 hours; the deduplication guide walks through the setup.
Where your own click ID fits
The ttclid is a return address. It exists only for TikTok traffic and only TikTok can read it, which is fine for sending a conversion back to TikTok and useless as the key your reporting depends on. That key should be a click ID you generate yourself, one per click, whatever platform sent it.
DropCPL works with Meta only and doesn’t connect to TikTok Ads. On Meta traffic it logs its own click_id with the ad_id, campaign_id and fbclid on the landing page’s domain, and sets the first-party cookie in the same response that renders the landing page.
Related terms
- fbclid: Meta’s equivalent
- gclid and msclkid: the Google and Microsoft versions
- gbraid and wbraid: what Google sends instead of gclid on some iOS clicks
- Tracking identifiers: why the key should be yours