In addition to the cookies set on our own sites, we utilize cookies for our Site Statsfeature. This tallies the unique numbers of visitors to a site, as well as the number from specific geographic locations. A visitor is counted when we see a user or browser for the first time in a given period.
Below are examples of the cookies set by Automattic, with explanations of their purpose. Some of these cookies are set across our whole network, whereas some are specific to individual services (e.g. WordPress.com, Longreads, etc). Please note that this is not an exhaustive list, but rather aims to be representative. Information about cookies that may be set by third parties, such as our ads partners, is below.
In addition, people and companies that use our services to publish or host their own sites may place additional cookies. We provide more information on these cookies below.
|Tracks if a visitor has clicked an ad before.
|Counts and tracks pageviews on Longreads.com. Used to determine whether or not to show our Membership popup message.
|Reduces the display of ads for repeat visitors.
Please also see the section below on third party advertisements that you may see on our sites or sites that use our services.
Analytics and Performance
|Used in log of Polldaddy survey data to aid in debugging customer problems
|Used for “AB testing” of new features.
|Identifies which user signup flow was shown to the user.
|tk_ni / tk_ai / tk_qs
|Gathers information for our own, first party analytics tool about how our services are used. A collection of internal metrics for user activity, used to improve user experience.
|Remembers the ID of the affiliate that referred the current user to WordPress.com
|utma / utmb / utmc / utmt / utmz / ga / gat / gid
|Google Analytics. Gathers information that helps us understand how visitors interact with our websites, which allow us to create a better experience for our visitors. Our users may also implement Google Analytics on their own websites.
|Authentication for Longreads.com Member accounts. Only active when logged in, on *.longreads.com domains.
|Stores whether a user has chosen to view the mobile version of a website.
|Used to track the language a user has selected to view popular blogs in.
|Defines the currency displayed in WordPress.com landing pages.
|Records last used folder in Polldaddy dashboard so it can be reopened upon user’s next visit.
|Login cookie used to identify Polldaddy user.
|Checks whether or not the current visitor is a logged in WordPress.com user.
|Persists a user’s wp-admin configuration.
|Tracks whether or not a user has already performed an action.
|Python/Ajax security cookie used on accounts.longreads.com.
|Used in order to determine whether or not the cookie banner should be shown. Set immediately on page load and retained for 6 hours to remember the visitor’s country.
|Remembers the state of visitor acceptance to the cookie banner. Only set when the visitor clicks Accept.
|Set when the user is logged in using two factor authentication.
|Checks if cookies are enabled to provide appropriate user experience.
Visitors to Sites with Jetpack installed
Below are examples of the cookies set for visitors to sites with the Jetpack plugin installed. For more details on the cookies set for administrators, please see https://jetpack.com/support/cookies/.
Our Internal Analytics Tool
In order to better understand how our services are used, we monitor certain user activities that take place within our products, including page views and clicks on any links used when managing a site via our dashboards.
We call each one of these actions an “event.” Analytics events are attached to your WordPress.com account and are handled via a first party system that Automattic owns and maintains. In general, we record the following data for each event: IP address, WordPress.com user ID and username, WordPress.com-connected site ID (for sites not hosted on WordPress.com), user agent, referring URL, timestamp of event, browser language, and country code.
You may opt out of our analytics program through your user settings. By doing so, you won’t share information with our analytics tool about events or actions that happen after the opt-out, while logged in to your WordPress.com account. Note that opting out does not disable the functionality of the actions we track – for example, if you publish a post, we will still have record of that (don’t worry!), but for an event or action after you opt out, we will not have other data associated with that action or event in the analytics tool.