What is the tk_or cookie?
tk_or is an HTTP cookie created by Jetpack, the security, performance, and statistics plugin developed by Automattic for WordPress websites. It appears in a visitor's browser when they access a WordPress site that has the Jetpack Stats (traffic statistics) module enabled.
The cookie is part of a broader set of tk_-prefixed cookies (such as tk_ai, tk_qs, tk_lr) used by Jetpack to measure traffic and visitor behavior in aggregate.
What data it stores
tk_or generally stores information about the external page or site the visitor arrived from (the origin referrer), so that traffic sources can be correctly attributed in statistics reports. The exact value format may vary and is not publicly documented in detail by Automattic.
The collected data is sent to Jetpack/WordPress.com (Automattic) servers, which aggregate it to generate the statistics reports shown in the site's admin dashboard.
What it is used for
The main purpose of tk_or is to help site administrators understand where visitors are coming from — an external site, a social network, or a search engine — in order to evaluate the effectiveness of promotion channels.
For Automattic/Jetpack, this data supports the statistics module offered as part of the plugin's functionality, and is not directly tied to advertising services.
Does it require consent?
Under CookieFix's classification, tk_or falls under the statistics (analytics) category. Because it tracks visitor behavior across sessions and attributes traffic sources, it does not qualify as a "strictly necessary" cookie under the ePrivacy Directive (2002/58/EC) and requires prior user consent under the GDPR.
Site administrators must list this cookie in their cookie policy, classify it correctly under the statistics category in the consent banner, and ensure the Jetpack script that sets it does not run before the visitor has given consent.
How to block or delete tk_or
A visitor can delete or block tk_or through browser settings (Chrome, Firefox, Safari, Edge) by clearing the site's cookies or enabling blocking of third-party/statistics cookies. Anti-tracking browser extensions can also prevent it from being set.
- Site administrators can disable the Jetpack Stats module in the plugin settings if they don't want to collect this data.
- Alternatively, they can use a consent management platform (CMP) like CookieFix, which automatically blocks Jetpack's statistics scripts until the visitor accepts the "statistics" category in the banner.
Frequently asked questions
It's a statistics cookie set by Jetpack (Automattic) on WordPress sites, used to identify the external traffic source of a visitor.
Its typical duration is 5 years, though it may be renewed on each visit.
Yes, since it's a statistics cookie, it requires prior consent under GDPR and ePrivacy rules, as it is not strictly necessary for the site to function.
You can disable the Jetpack Stats module or use a CMP that blocks Jetpack's statistics script until consent is obtained.