The _ttp cookie
The TikTok Pixel's browser identifier, used to measure ad campaigns and link site events to the same visitor.
_ttp at a glance
- Cookie name
_ttp- Vendor
- TikTok Pixel
- Category
- Advertising
- Party
- First-party or third-partyObserved across TagPipes scans, not taken from vendor documentation.
- Typical duration
- 13 months from last use
- Set on
.<your-domain> (and .tiktok.com)- Value format
- Opaque identifier (format not documented by vendor)
- Name match
- Exactly
_ttp
What the _ttp cookie does
The TikTok Pixel sets _ttp on the advertiser's own domain to identify the browser. TikTok uses it to measure and improve ad campaign performance and to personalize ads on TikTok, by linking site events to the same visitor.
TikTok documents a lifetime of 13 months from the last date it was used, so it rolls forward with activity rather than expiring from creation. First-party cookies can be turned off in the Pixel settings. TagPipes saw _ttp set both on sites' own domains and as a third-party cookie, which is why both are listed.
What TagPipes observed
0.76%
of sites scanned set it (312 of 41,162)
390 days
median observed lifetime
TagPipes scanned 41,162 public websites between August 11, 2026 and September 13, 2026, loading up to three pages per site in a real browser as a first-time visitor. _ttp was present on 312 of them.
It was set as a first-party cookie on 273 sites and as a third-party cookie on 294. A site can count in both. Where it was stored as a persistent cookie, the median lifetime we recorded was 390 days.
Often found alongside
- ttcsid 92%
- ttcsid_* 92%
- _ga 90%
- _ga_<container-id> 89%
- _tt_enable_cookie 88%
- _gcl_au 82%
Percentage of sites with _ttp where the other cookie was also present.
Technologies detected on the same sites
- TikTok Pixel on 99% of them (0.76% of all sites scanned)
- Google Analytics on 97% of them (55% of all sites scanned)
- Meta Pixel on 87% of them (13% of all sites scanned)
- DoubleClick on 80% of them (11% of all sites scanned)
- Google Tag Manager on 80% of them (30% of all sites scanned)
Aggregate figures across all sites scanned. Websites of TagPipes customers are excluded, no individual site is named, and cookie values are never read or stored. Snapshot dated September 13, 2026.
How to check for _ttp on a website
- Open the site in Chrome, then open DevTools (F12, or Cmd+Option+I on a Mac).
- Go to the Application tab and expand Cookies in the left panel.
- Select each domain listed there and look for
_ttp. The Expires column shows when it will be deleted. - If it is not there, reload the page. Many cookies are only set after a tag has loaded, and some only after a visitor has made a consent choice.
Sources
Purpose, duration and value format checked against the vendor documentation above on . The observed party and the figures under What TagPipes observed are TagPipes scan data from September 13, 2026, not values documented by the vendor. Vendors change their cookies, and sites can configure their own names and lifetimes. Browse all cookies.
Know every cookie your own site sets
TagPipes Pulse identifies the cookies dropped on your site and flags unclassified or miscategorized ones. Shield builds your cookie declaration from a real scan rather than a questionnaire.
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Rawsoft's expertise is technology, not law; please confirm any regulatory interpretation with your own counsel.