Kameleoon bills your account on an annual basis based on the average number of monthly unique users who visited your site or application in the previous 12 months.
Kameleoon automatically excludes bot traffic from your campaign results. Lean more about it here.
Kameleoon has a native consent management and therefore only collects data from users who have given their consent. Learn more about Kameleoon’s consent management policy
The measurement of unique users is based on cookies. A cookie is a file placed on a browser that contains an anonymous unique identifier, called the Kameleoon visitorcode, randomly assigned to a user. This ID is used to uniquely identify a browser. Our visitorcode is stored during 365 days on the user’s browser.
Kameleoon determines unique users using the visitorCode randomly assigned to a visitor of your web or mobile application by our SDKs, each time a bucketing or tracking event is sent for a unique user ID:
- When the isFeatureFlagActive(), getFeatureVariationKey() or getFeatureVariable() methods are used and the user is bucketed into a feature flag.
- When the trackConversion() method is used to track goals conversion. Users are only counted once, even if they are bucketed into different experiments / feature flags across devices.
If you rather use your own user ID instead of our visitorCode, our SDKs will use it to uniquely identify your users across devices. If you use both Kameleoon Web Experimentation and Feature Experimentation, you can override anonymous Kameleoon visitorCode with your own user ID to avoid overcounting.