BEYABLE Analytics
How to configure BEYABLE 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, Personalise the website
Overview
This guide explains how to implement different privacy configurations for BEYABLE Analytics 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. BEYABLE Analytics tracker on a website. BEYABLE is a French company.
What the service does in this scope. BEYABLE Analytics collects a random visitor ID generated by the solution (used to count sessions), terminal and browser type, city-level location and content interactions. Two settings change what the tracker stores and sends: segment deactivation (aggregate statistics without user characteristics that could build segments) and cookie opt-out (page hits without session or visitor IDs), each set globally in the script or per user via an opt-out option. BEYABLE processes data only on the client's behalf (processor).
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Cookie opt-out and segment deactivation globally: hits without visitor or session IDs. |
| Configuration B — Medium risk (⚠ no-consent) | Exempt mode: visitor ID for session counting; segments deactivated. |
| Configuration C — Higher risk | Segments active (for personalisation), after consent. |
⚠ Recommendation — exemption is self-assessed and France-specific. CNIL treats audience-measurement cookies as exempt from consent only where they serve solely the publisher's audience measurement, produce anonymous statistics, are not cross-referenced or passed on, and do not allow tracking across sites; it recommends a cookie lifetime of about 13 months without automatic extension and data retention of at most 25 months. CNIL now offers a self-evaluation tool rather than an approval programme, so describe the configuration as a self-assessed exemption. § 25 TDDDG in Germany contains no equivalent exemption. Run B without consent only after review by your DPO or independent counsel.
Step 1 — Configure BEYABLE Analytics
| # | Configuration area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk (⚠ no-consent) | Configuration C — Higher risk |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service | Improve the service; Personalise the website |
| 2 | Cookie opt-out (global) | Script tracking-mode parameter | On | Off | Off |
| 3 | Segment deactivation (global) | Script tracking-mode parameter | On | On | Off |
| 4 | Per-user opt-out | Opt-out option on the website | Provide | Provide | Consent withdrawal |
| 5 | Loading | Consenter | Without consent (no identifiers) | See ⚠ recommendation | After consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk (⚠ no-consent) | Configuration C — Higher risk |
|---|---|---|---|
| Processing purposes | Improve the service | Improve the service | Improve the service, Personalise the website |
| Tracking method | No tracking | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | No identifier | Device identifiers | Device identifiers |
| Data categories | Aggregated site statistics, Browsing and interaction data, Device characteristics | Aggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, Non-precise location data | As B, plus Users' profiles |
| Legal role of data recipient | Processor | Processor | Processor |
| Personalisation model | No personalisation | No personalisation | Group based (behaviour) |
| Maximum storage duration | Per DPA | Per DPA | Per DPA |
| Processing location | Per DPA | Per DPA | Per DPA |
Privacy-policy follow-up
- BEYABLE as processor; mode used; opt-out option; segments (C).
Verification checklist
- A: no visitor or session ID sent.
- Per-user opt-out implemented.
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