Set up your bannerConfigure Your ToolsAnalytics

Cloudflare Web Analytics

How to configure Cloudflare Web Analytics 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 reflect Cloudflare Web Analytics in the Consenter Manager. Cloudflare's CDN, DNS, WAF and bot-management functions are strictly necessary infrastructure and are out of scope. Web Analytics has no visitor-facing privacy settings, so this guide uses a single fixed-behaviour table.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.

At a glance

Scope. Cloudflare Web Analytics, collected via the JavaScript beacon or at Cloudflare's edge.

What the service does in this scope. Web Analytics does not use client-side state such as cookies or localStorage to collect usage metrics, and Cloudflare states it does not fingerprint individuals via IP address or user agent for analytics. It counts "visits" based on referrer rather than unique visitors.

⚠ Recommendation. No device storage is used, but the beacon is still loaded from Cloudflare and page-view data is transmitted to a US company. If you load it without consent, treat this as a self-assessed exemption and have your DPO confirm the legal basis (GDPR) separately from the device-access question (§ 25 TDDDG). Otherwise load it after Consenter consent.

Step 1 — Implement Cloudflare Web Analytics

Configuration areaFixed behaviour / required action
Processing purposesImprove the service
CollectionJavaScript beacon or edge collection
LoadingAfter Consenter consent, or without consent per the ⚠ note
ContractCloudflare DPA

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesImprove the service—
Tracking methodNo trackingNo client-side state
IdentifierNo identifierNo fingerprinting
Data categoriesAggregated site statistics, Device characteristicsPage views, referrers, performance
Legal role of data recipientProcessorCloudflare DPA
Personalisation modelNo personalisation—
Maximum storage durationPer Cloudflare documentation—
Processing locationUnited StatesUS enterprise; CLOUD Act

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