Chartbeat
How to configure Chartbeat at different risk levels and map it in the Consenter Manager.
This work is licensed under CC BY-SA 4.0
Typical processing purposes: Improve the service
Overview
This guide explains how to implement different privacy configurations for Chartbeat and how to reflect them in the Consenter Manager.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. Chartbeat content analytics script on publisher websites. Chartbeat, Inc. is a US company.
What the service does in this scope. Chartbeat acts as a data processor; it obtains IP addresses and certain online identifiers but states it does not store IP addresses. Cookies include _cb (site-specific visitor ID, 395 days) and _chartbeat2 (visit timing to distinguish new, returning and loyal visitors, 395 days). Setting _sf_async_config.noCookies = true prevents _chartbeat2 from being created. Visitors can opt out via Chartbeat's opt-out page (_cb_optout).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | noCookies enabled; after consent. |
| Configuration B — Higher risk (default) | Cookies _cb and _chartbeat2 (395 days); after consent. |
No configuration without prior consent. Chartbeat runs a script that sends frequent pings with engagement data; no consent-free configuration is documented.
Step 1 — Configure Chartbeat
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk (default) |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service |
| 2 | Cookies | _sf_async_config.noCookies | true | false (default) |
| 3 | Loading | Consenter script blocking | After consent | After consent |
| 4 | Opt-out | Link to Chartbeat opt-out page | Provide | Provide |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Chartbeat, Inc. is a US company subject to the US CLOUD Act.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk (default) |
|---|---|---|
| Processing purposes | Improve the service | Improve the service |
| Tracking method | First party tracking (single session) | First party tracking (cross-session) |
| Identifier | IP address | Device identifiers, IP address |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics, IP address | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Not documented | 395 days (cookies) |
| Processing location | United States | United States |
Privacy-policy follow-up
- Chartbeat as processor; engagement measurement; cookies (B); opt-out page; US processing and potential access by US authorities.
Verification checklist
- No
chartbeat.com/chartbeat.netrequests before consent. - A:
_chartbeat2absent.
How is this guide?
Shape Consenter Together
Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.
Need Help?
Last updated on