What is the __kla_id cookie?
When Klaviyo’s JavaScript is enabled, the __kla_id cookie can track and identify site visitors through an auto-generated ID. This cookie can temporarily hold personally identifiable information. Once a visitor is identified, the cookie can pass their data into Klaviyo.
Our October 2026 scan found it on 3 sites (0% of the 2,450 we scanned), set before any consent.
- Purpose
- Advertising
- Belongs to
- Klaviyo
- Set as
- First-party (under the site's own domain)
- Typical lifetime
- 13 months (vendor says: 2 years) — shorter than the vendor documents
Sites that set __kla_id before consent
The highest-ranked 3 of 3 sites.
- woocommerce.com5 tracking companies
- comodo.com6 tracking companies
- nanit.com6 tracking companies
How to stop it
Declining non-essential cookies in a site's consent banner should stop __kla_id being set on later visits. Blocking third-party cookies in your browser settings stops the third-party kind everywhere, and clearing cookies for a site removes any it already set.
Description from the Open Cookie Database (Apache 2.0).
Understanding this page
- How cookie lifetimes work, and why a 13-month _ga matters
What a cookie's "expires" field actually controls, why Google Analytics ships a 2-year default that many sites cut down to 13 months, and how Safari's 7-day cap on script-set cookies changes the picture.
- First-party vs third-party cookies (and why "first-party" still tracks you)
What the distinction actually means technically, why browsers only block one of the two, and how CNAME cloaking, server-side tagging and cookies like _ga let sites keep tracking under their own domain.
- How to block or limit trackers
Browser privacy settings, content blockers, Global Privacy Control and clearing cookies compared honestly — what each one actually stops, what it doesn't, and what it costs you in return.