Kameleoon
How to configure Kameleoon 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 Kameleoon 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. Kameleoon web experimentation and personalisation (JavaScript tag).
What the service does in this scope. Kameleoon stores the kameleoonVisitorCode identifier. The consent management policy is set in Admin > Projects. With Consent required, Kameleoon starts in restricted mode and switches to normal mode when Kameleoon.API.Core.enableLegalConsent is called, remembering the choice for the visitor. Consent can be granted separately for AB_TESTING and PERSONALIZATION. For certain rule types, Kameleoon recommends classifying Kameleoon as a "strictly necessary cookie" so that they run without consent.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Consent required; enableLegalConsent("AB_TESTING") only. |
| Configuration B — Higher risk | Consent required; enableLegalConsent("BOTH") (testing and personalisation). |
⚠ Recommendation — "strictly necessary" classification is legally uncertain. Kameleoon's suggestion to run some rules as strictly necessary has no basis in this guide's sources for German or EU law. Do not classify Kameleoon as strictly necessary without review by your DPO or independent counsel.
Step 1 — Configure Kameleoon
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Improve the service | Improve the service; Personalise the website |
| 2 | Consent management policy | Admin > Projects | Consent required | Consent required |
| 3 | Consent signal | enableLegalConsent(type) / disableLegalConsent(type) | AB_TESTING | BOTH |
| 4 | Loading | Tag in restricted mode until consent; or Consenter blocking | Restricted until consent | Restricted until consent |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Improve the service | Improve the service, Personalise the website |
| Tracking method | First party tracking (cross-session) | First party tracking (cross-session) |
| Identifier | Device identifiers | Device identifiers |
| Data categories | Browsing and interaction data, Device characteristics, Device identifiers | As A, plus Users' profiles |
| Legal role of data recipient | Processor | Processor |
| Personalisation model | No personalisation | Group based (behaviour) |
| Maximum storage duration | Not documented | Not documented |
| Processing location | Per DPA | Per DPA |
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