Features Pricing GDPR cookie banner Google Consent Mode v2 WordPress plugin Cookiebot alternative For Agencies GDPR ePrivacy About Contact
RO | EN
Start Free →
Statistics

_chartbeat2 Cookie (Chartbeat) – What It Is & Does

_chartbeat2 is an HTTP cookie set by the Chartbeat analytics service, used to recognize returning visitors and measure real-time traffic and engagement on a website. It is a statistics cookie, not strictly necessary, so it requires visitor consent under EU/Romanian law.

Name
_chartbeat2
Provider
Chartbeat
Category
Statistics
Type
HTTP cookie
Lifetime
13 months
Consent
Yes, before it is set (GDPR / ePrivacy)

What is the _chartbeat2 cookie?

_chartbeat2 is a first-party cookie placed by the Chartbeat analytics script on websites that use this service to track traffic and reader engagement in real time.

It appears as soon as a visitor loads a page where the Chartbeat tracking code is installed, typically in the site header or footer, regardless of whether the visitor actively interacts with the content.

What data it stores

The cookie stores a unique identifier associated with the visitor, which Chartbeat uses to distinguish new visitors from returning ones and to aggregate longer-term traffic data.

The exact value is an alphanumeric string generated by Chartbeat; its internal format may vary and is not publicly documented in detail. The data is sent to Chartbeat's servers for processing and reporting back to the site publisher.

What it is used for

For Chartbeat, the cookie helps build statistics on unique visitors, return visits, and content engagement (time on page, scrolling, attention).

For the site owner, this data supports editorial and marketing decisions — which articles perform well, how the audience evolves in real time, and where traffic comes from.

Does it require consent?

In CookieFix's classification, _chartbeat2 falls under the statistics (analytics) category. It is not strictly necessary for the site to function, so under the ePrivacy Directive (transposed in Romania via Law 506/2004) and GDPR, it requires prior, informed, freely given visitor consent before being set.

  • It must be clearly listed in the site's cookie policy (name, provider, purpose, duration).
  • It cannot be activated automatically on page load — only after the visitor accepts the „statistics” category in the consent banner.
  • Site owners must allow consent to be withdrawn as easily as it was given.

How to block or delete _chartbeat2

A visitor can manually delete or block _chartbeat2 from their browser's privacy/cookie settings (Chrome, Firefox, Edge, Safari), usually under the section for site data.

For site owners, the recommended approach is a consent management platform (CMP) like CookieFix, which automatically blocks the Chartbeat script before the visitor gives consent and only loads it after the „statistics” category is accepted.

Frequently asked questions

It does not store sensitive data; it holds an identifier used for traffic statistics, though it is still considered indirectly identifiable personal data under GDPR.

The typical duration is around 13 months from the last time it was set or updated, based on Chartbeat's stated practice.

Yes, as a statistics cookie it requires the visitor's prior consent under GDPR and the ePrivacy rules.

The Chartbeat script should not set the cookie, and that visitor will not be included in the site's traffic statistics.

Updated 8 September 2026 · Information comes from the provider’s public documentation and CookieFix scans; it is not legal advice.