Measurement models
Kameleoon offers three measurement models. The main difference between them is whether you pay for your potential traffic or your actual campaign engagement, and for engagement-based plans, whether your quota renews every month or arrives as a single annual grant.Monthly Unique Users (MUU)
The MUU model (standard for Enterprise plans) is based on the total traffic visiting your website or application.- How it works: Kameleoon calculates your usage based on the average number of unique monthly visitors over a 12-month period. It counts a user as soon as they visit your site, regardless of whether they interact with an experiment.
- Why choose it?: It provides cost predictability. Because you pay based on total traffic, you can run unlimited experiments and allocate 100% of your traffic to them without additional costs.
- Best for: Teams that run many experiments or high-traffic tests and want to avoid worrying about “spending” a quota on every test.
Monthly Tracked Users (MTU)
Kameleoon bases the MTU model (standard for Starter plans) on campaign engagement.- How it works: Kameleoon only counts a user as an MTU when they interact with an active campaign, such as an experiment or a feature flag.
- Why choose it?: It provides cost flexibility. You only pay for the visitors you actually “touch” with your experiments. This model is ideal if you only test on specific visitor segments or low-traffic journeys.
- The trade-off: Pushing high-traffic experiments (like a 100% allocation to a winning variant) or experiencing traffic spikes in an experiment will consume your MTU quota faster.
- Best for: Brands with selective testing needs or those who want to scale their costs exactly with their testing activity.
Annual Tracked Users (ATU)
The ATU model uses the same engagement-based pricing as MTU, but grants your entire year’s quota upfront instead of resetting it every month.- How it works: Kameleoon multiplies your monthly MTU allowance by 12 and grants that full amount as a single pool at the start of your annual contract period. For example, a plan with a 100,000 MTU monthly allowance receives 1,200,000 ATU upfront. You draw down against this pool as visitors interact with your experiments and feature flags, using the same de-duplication and visitor-identification logic as MTU.
- Why choose it?: It removes the monthly reset, so you can front-load testing during peak periods and taper off later without losing access to capacity you didn’t use in a given month.
- The trade-off: Your quota doesn’t renew until your contract renews, so spending it faster than a 12-month pace leaves you without capacity for the rest of the period. For example, if you exhaust your pool after 9 months, you cannot run new experiments or feature flags for the remaining 3 months unless you upgrade to a higher plan.
- Best for: Brands with seasonal or uneven testing activity who want flexibility in when they use their quota, not just how much they use.
Model comparison at a glance
Web Experimentation
Kameleoon measures users based on cookies. A cookie is a file that the system places in a browser that contains an anonymous unique identifier, called the Kameleoonvisitorcode, randomly assigned to a user. Kameleoon uses this ID to identify a browser. A visitorcode is stored for 365 days on the user’s browser.
Feature Experimentation
Refer to this FAQ in our developer documentation for more information on how Kameleoon counts and tracks unique users in Feature Experimentation.MTU details
MTU represents the number of unique visitors exposed to at least one Kameleoon experiment or feature flag within a calendar month. Kameleoon uses the following logic to count MTUs:- De-duplication: Kameleoon counts each visitor only once per calendar month, regardless of how many times they visit your site or how many experiments they trigger. For example, if a user participates in three different experiments in one month, they still only count as one MTU.
- Visitor Identification:
- Anonymous visitors: Kameleoon identifies anonymous visitors using a unique
visitorcodestored in a browser cookie. - Identified visitors: If you provide a custom unique ID (such as a login ID), Kameleoon can de-duplicate those users across different devices and browsers, ensuring they only count as one MTU.
- Anonymous visitors: Kameleoon identifies anonymous visitors using a unique
- Monthly Reset: Your MTU count resets to zero at the beginning of each calendar month.
View MTU counts
You can view your current MTU count on the Organization page (click Admin and select Organization).
Threshold notifications
Kameleoon displays warning banners and sends email notifications when you reach the following thresholds:- 90% of the MTU limit.
- 100% of the MTU limit.
- Three days after reaching 100% of the MTU limit.
Reaching the limit
If you reach the MTU limit, Kameleoon grants a three-day grace period to request an upgrade. If you do not upgrade within that period, Kameleoon automatically pauses all active campaigns. When Kameleoon pauses campaigns, the MTU count resets at the end of the monthly period, and paused campaigns automatically resume.ATU details
ATU uses the same engagement-based measurement as MTU, except Kameleoon grants your quota once per year instead of resetting it every month. Kameleoon uses the following logic to count ATUs:- Annual allocation: Kameleoon grants your full annual quota, 12 times your monthly MTU allowance, as a single pool at the start of your contract period, instead of granting a smaller quota every month.
- De-duplication: Kameleoon counts each visitor using the same engagement-based de-duplication logic as MTU, then draws that usage from your annual pool rather than a monthly quota.
- Visitor identification: Kameleoon identifies anonymous visitors through a
visitorcodecookie and de-duplicates identified visitors across devices using a custom unique ID, exactly as it does for MTU.