Set up your bannerConfigure Your ToolsAudience Measurement

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.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. 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.

ConfigurationSummary
Configuration A — Medium risknoCookies 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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk (default)
1Processing purposesOperator decisionImprove the serviceImprove the service
2Cookies_sf_async_config.noCookiestruefalse (default)
3LoadingConsenter script blockingAfter consentAfter consent
4Opt-outLink to Chartbeat opt-out pageProvideProvide

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 fieldConfiguration A — Medium riskConfiguration B — Higher risk (default)
Processing purposesImprove the serviceImprove the service
Tracking methodFirst party tracking (single session)First party tracking (cross-session)
IdentifierIP addressDevice identifiers, IP address
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristics, IP addressAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, IP address
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationNot documented395 days (cookies)
Processing locationUnited StatesUnited 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.net requests before consent.
  • A: _chartbeat2 absent.

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

On this page