Set up your bannerConfigure Your ToolsAnalytics

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.

  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. 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.

ConfigurationSummary
Configuration A — Lower riskCookie 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 riskSegments 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 areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk (⚠ no-consent)Configuration C — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the serviceImprove the service; Personalise the website
2Cookie opt-out (global)Script tracking-mode parameterOnOffOff
3Segment deactivation (global)Script tracking-mode parameterOnOnOff
4Per-user opt-outOpt-out option on the websiteProvideProvideConsent withdrawal
5LoadingConsenterWithout consent (no identifiers)See ⚠ recommendationAfter consent

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium risk (⚠ no-consent)Configuration C — Higher risk
Processing purposesImprove the serviceImprove the serviceImprove the service, Personalise the website
Tracking methodNo trackingFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierNo identifierDevice identifiersDevice identifiers
Data categoriesAggregated site statistics, Browsing and interaction data, Device characteristicsAggregated site statistics, Browsing and interaction data, Device characteristics, Device identifiers, Non-precise location dataAs B, plus Users' profiles
Legal role of data recipientProcessorProcessorProcessor
Personalisation modelNo personalisationNo personalisationGroup based (behaviour)
Maximum storage durationPer DPAPer DPAPer DPA
Processing locationPer DPAPer DPAPer 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

On this page