Set up your bannerConfigure Your ToolsA/B Testing and Personalisation

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.

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

ConfigurationSummary
Configuration A — Medium riskConsent required; enableLegalConsent("AB_TESTING") only.
Configuration B — Higher riskConsent 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 areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionImprove the serviceImprove the service; Personalise the website
2Consent management policyAdmin > ProjectsConsent requiredConsent required
3Consent signalenableLegalConsent(type) / disableLegalConsent(type)AB_TESTINGBOTH
4LoadingTag in restricted mode until consent; or Consenter blockingRestricted until consentRestricted until consent

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesImprove the serviceImprove the service, Personalise the website
Tracking methodFirst party tracking (cross-session)First party tracking (cross-session)
IdentifierDevice identifiersDevice identifiers
Data categoriesBrowsing and interaction data, Device characteristics, Device identifiersAs A, plus Users' profiles
Legal role of data recipientProcessorProcessor
Personalisation modelNo personalisationGroup based (behaviour)
Maximum storage durationNot documentedNot documented
Processing locationPer DPAPer 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

On this page