Kameleoon
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Kameleoon SAS · www.kameleoon.com
Compare with Optimizely → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Kameleoon at a glance
- Vendor
- Kameleoon SAS
- Headquarters
- Incorporated in France source, captured 16 Nov 2026
- Data hosting
- In the EU by default source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Kameleoon 2.5/5, the mean of 6 judges. Kameleoon, an experimentation and personalisation platform from Kameleoon SAS of Paris, scored strongest on data and integrations and statistical rigour, and weakest on consent and tracking. how scores are made
- As of
- Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Kameleoon, an experimentation and personalisation platform from Kameleoon SAS of Paris, scored strongest on data and integrations and statistical rigour, and weakest on consent and tracking. Judges credit the vendor's own pages for naming a guardrail set — sequential testing, multiple testing correction, automatic sample ratio mismatch detection, CUPED as a paid add-on — and for a BigQuery integration documented down to hourly polling and a daily merge, alongside a segment-export API with bearer authentication. Experimentation scope sits at 6–7. The clearest split is performance impact, scored 2 to 5: the higher scores credit a published snippet figure of under 70 ms alongside 99.99% uptime, while the lower scores note that the dedicated flicker and performance documentation pages were captured without readable text. On consent and tracking, two rationales decline to rate for lack of public information, with the remaining scores at 2–3. Sovereignty scores cluster at 4: a French entity, French law and a German host are named, but the pricing page shows data residency as 'EU or US' with no default stated.
Speaks for it
- The vendor's own pages name a guardrail set — sequential testing, multiple testing correction, automatic sample ratio mismatch detection — with CUPED available as an add-on
- BigQuery goals pull conversion data on a schedule with hourly polling and a daily merge, and BigQuery metrics display as KPIs on results pages
- A segment-export endpoint is documented with bearer authentication, pagination and filtering
- The experimentation surface spans A/B and multivariate tests, server-side and mobile app testing, feature flags with progressive rollout, and mutually exclusive groups with holdouts
- A free 30-day trial requires no credit card and allows up to 3 experiments, and the Starter tier states 10 experiments and 50,000 visitors per month
Held against it
- We found no public information on when the testing script runs relative to consent or which cookies and storage keys it sets, with the consent-management documentation pages captured without readable text (consent and tracking scored 0 to 3)
- The only published performance figure is the pricing-page claim of 99.99% uptime and a snippet loading under 70 ms, with no measurement conditions attached (performance impact scored 2 to 5)
- No price figure appears on the captured pages for any paid tier; Enterprise is priced custom and add-ons from Personalization to CUPED carry no price (pricing transparency scored 2 to 4)
- The pricing page offers data residency of 'EU or US' (Enterprise: 'EU or US or Custom') with no default region stated, and we found no public information on a data processing agreement or a published subprocessor list
- Data warehouse integrations are a premium add-on requiring contact with a Customer Success Manager, and we found no public information on visitor-level raw export or stated API limits
Best for
- You want to measure experiments against your own warehouse data — BigQuery goals pull conversions on a schedule and two-way sync is offered — and can treat the warehouse piece as a premium add-on
- You need one platform covering web, mobile app and feature-release testing, with SRM detection and sequential testing named on the entry tier
- You want a no-code or prompt-based start for a marketing team — a free 30-day trial, no credit card required, up to 3 experiments
Avoid if
- You run EU traffic and need the script's consent behaviour in writing before launch — the homepage markets bypassing Safari ITP and ad blockers for full traffic visibility, and the consent-management pages were captured without readable text
- You need a verified page-speed impact with methodology — the only published figure is a pricing-page claim of a snippet loading under 70 ms with no measurement conditions attached
- You must compute an annual cost from public pages — ask the vendor: the public pages we read do not show it
- You require EU hosting as a confirmed default for visitor data — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 3.5 of 5 |
| Statistical method & guardrails | 3.5 of 5 |
| Consent & visitor tracking | 1.5 of 5 |
| Snippet performance & flicker | 2 of 5 |
| Analytics, data export & integrations | 3.5 of 5 |
| European sovereignty | 2 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The vendor documents a prompt-based and visual editor a marketing team can drive without developers, alongside server-side testing, mobile app testing, multivariate experiments, feature flags with progressive rollout, targeting on more than 40 user properties, and mutually exclusive groups with holdouts — targeting well past the URL. We found no public information on multi-page tests or on personalisation being tested against its own control, and the SDK documentation appears only as page titles without captured content, so I hold back one step. 1 2 4 7
The E-Commerce Manager
The captured pages show A/B and multivariate testing through graphic or code editors or SDKs, server-side and mobile app testing, feature flags with progressive rollout, and mutually exclusive groups with holdouts — enough coverage to test web, app and feature releases. I found no public information on multi-page tests or on personalisation that is itself tested against a control, which is the exact check I want before trusting a personalised product page, so it stops below the top level. 1 2 4
The Product Engineer
This is the shape of platform I want: the vendor's own pages name server-side testing, mobile app testing, multivariate tests, feature flags with progressive rollout, mutually exclusive groups and holdouts, and personalisation, all on one back-office. It stays short of the top band because the captured pages never enumerate which languages the SDKs cover, and I found no public information on multi-page tests, edge delivery, or a documented experiment lifecycle with a searchable library of past results. 1 2 4
The CRO Consultant
The published pages show a full programme shape: A/B and multivariate tests through graphic or code editors or SDKs, server-side and mobile app testing, feature flags with progressive rollout, mutually exclusive groups with holdouts, and personalisation as its own module. The captured pages do not document multi-page tests or personalisation measured against a control, so I place it just below the top tier. 1 2 4
The Data Protection Officer
The vendor's own pages document A/B testing with graphic or code editors and SDKs, multivariate and server-side testing, mobile app testing, feature flags with progressive rollout, mutually exclusive groups and holdouts, and personalisation as an add-on module. We found no public information on multi-page tests or on personalisation that can itself be tested against a control, so the documented breadth sits above the mid-level but not at the top. 1 2 4
The Skeptic
The claimed scope is broad — graphic and code editors plus SDKs, server-side testing, mobile app testing, multivariate experiments, mutually exclusive groups with holdouts, and personalisation — but nearly all of it is asserted on the homepage and pricing page rather than shown in readable documentation. The legal notice independently describes variations built through graphic or code editors or SDKs, which corroborates the editor story and pulls this above the mid anchor. I stop short of the higher level because we found no public information on documented SDK languages, multi-page tests, or a searchable library of past results. 1 2 4 7 8
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
Sequential testing, multiple testing correction, sample ratio mismatch detection, CUPED and contextual multi-armed bandits are all named on the vendor's own pages — precisely the defences I want behind every uplift number I report to the board. We found no public information naming the underlying method (frequentist or Bayesian) with confidence or credible intervals, nor on guardrail metrics that could stop a harmful test. 1 2
The E-Commerce Manager
Sequential testing, multiple testing correction, automatic sample ratio mismatch detection and CUPED as a paid add-on are all named on the vendor's own pages, which is the guardrail set I look for before reading a winner. The captured text names no underlying method as frequentist or Bayesian and shows no confidence intervals or sample-size guidance, and I found no public information on guardrail metrics that can stop a harmful test. 1 2
The Product Engineer
The guardrail stack is named in the vendor's own words: sequential testing, multiple testing correction, and automatic sample ratio mismatch detection ship in the Starter tier, with CUPED listed among the add-ons. I found no public information on guardrail metrics that can stop a harmful test, and CUPED sits in the paid add-on list rather than the core engine, so this is strong but not the full protection set. 1 2
The CRO Consultant
Sequential testing, multiple testing correction, automatic sample ratio mismatch detection and CUPED (as a paid add-on) are all named on the plans page and homepage — most of the guardrail set I need before defending a readout to a client. The captured pages do not name the underlying method, show intervals per variant, or describe guardrail metrics that would stop a harmful test. 1 2
The Data Protection Officer
The plans page names sequential testing, multiple testing correction and sample ratio mismatch detection as included in the entry tier, with CUPED available as a paid add-on, and the homepage confirms mismatch detection is automatic. We found no public information on guardrail metrics that can stop a harmful test, on intervals per variant, or on sample-size and duration guidance. 1 2
The Skeptic
The vendor names exactly the guardrails I read for — sequential testing against peeking, multiple testing correction, automatic sample ratio mismatch detection, and CUPED as an add-on — which is more than most marketing pages admit to. But these appear as claims, not documentation: the pages on sample ratio mismatch and on choosing a statistical method were captured without readable text. We found no public information on the method being named as frequentist or Bayesian, confidence or credible intervals, sample-size guidance, or guardrail metrics that can stop a harmful test. 1 2 9 10
Consent & visitor tracking
n/r
n/r
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
The developer documentation includes a consent management page and a consent management policy page, but their content was not captured, so I cannot verify when the test script runs relative to consent or which cookies and storage keys it sets. The privacy policy's cookie provisions concern the vendor's own website, not the script running on our visitors' pages under §25 TDDDG. 3 11 12
The E-Commerce Manager
The privacy policy documents cookie purposes and the right to refuse cookies, but that covers the vendor's own website, not what the testing script stores on my visitors' devices. Dedicated documentation pages on consent management and a consent management policy exist, yet their captured content is not readable, so I cannot confirm the script can be held until consent. I found no public information on a cookieless mode, on storage keys with their lifetimes, or on the legal basis for testing under German consent rules. 3 11 12
The Product Engineer
Consent-management sections exist in both the developer docs and the user manual, and the privacy policy says visitors can refuse cookies, which is the level of a documented consent capability without anything visible beyond it. The captured pages show no list of the cookies or storage keys the testing script sets and no consent-pending or cookieless mode, and the homepage markets bypassing Safari ITP and ad blockers for full traffic visibility — a posture I would want answered in writing before running this on EU traffic. 1 3 11 12
The CRO Consultant not rated — no public information
We found no public information on when the testing script runs relative to consent, what it stores on a visitor's device, or whether a cookieless mode exists. Captured pages on consent management and the consent management policy produced no verifiable statements, and the privacy policy's cookie passages cover the vendor's own website rather than the product script. 3 11 12
The Data Protection Officer
The privacy policy acknowledges cookies on the vendor's own site with their purposes, says they can be refused at any time, and declares the processing to the CNIL. The captured pages never state when the testing script runs relative to the consent banner, and we found no list of the cookies or storage keys that script sets. The consent management documentation pages were captured without readable text, so a consent-pending mode, cookieless option and IP anonymisation remain undocumented in what we hold. 3 11 12
The Skeptic not rated — no public information
We found no public information on how the test script behaves relative to consent, what it stores on the visitor's device, or how visitor identifiers are handled under the German telemedia rules. The captured privacy policy covers only the vendor's own website cookies, and the consent management documentation pages were captured without readable text. 3 11 12
Snippet performance & flicker
panel disagrees
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
The plans page publishes a snippet that loads under 70 ms, and the developer documentation carries dedicated pages on flicker management and impact on website performance — though their content was not captured. I found no published figures for the flicker trade-off, script weight or Core Web Vitals impact, so I credit the load-time claim alone. 2 13 14
The E-Commerce Manager
The pricing page publishes a concrete figure — a snippet that loads under 70 ms alongside 99.99% uptime — and the documentation set includes pages on flicker management and on impact on website performance, but those captures show no readable text. So I have a promised load time without a methodology, and I found no public information on asynchronous loading, anti-flicker timeouts, self-hosting or Core Web Vitals impact. For a tenth of a second on my product page, that is not yet enough to plan on. 1 2 13 14
The Product Engineer
The plans page publishes a snippet load figure — under 70 ms alongside 99.99% uptime — and the developer docs carry dedicated pages on flicker management and on the impact on website performance, which is exactly where I would verify the anti-flicker mechanics. The captured pages show no script size, no Core Web Vitals measurements, and no self-hosting or first-party-domain option, though server-side testing does exist as an alternative path. 2 13 14
The CRO Consultant
The plans page publishes one figure — a snippet that loads under 70 ms with 99.99% uptime — which is more than most vendors put in writing. The captured flicker-management and website-performance documentation pages gave no verifiable statements, and the pages do not show asynchronous loading, script size, Core Web Vitals impact or a self-hosting option. 2 13 14
The Data Protection Officer
The only published figure is a claim on the plans page that the snippet loads under 70 ms alongside 99.99% uptime. We found no public information on asynchronous loading, flicker handling, timeout behaviour or Core Web Vitals impact; documentation pages on flicker management and website performance were captured but yielded no readable content. 2 13 14
The Skeptic
The only published figure is the pricing-page claim that the snippet loads under 70 ms alongside 99.99% uptime — a marketing number with no measurement conditions attached. The documentation set includes pages dedicated to flicker management and performance impact, but they were captured without readable content, and we found no public information on Core Web Vitals impact, script weight, self-hosting, or per-project bundles. 2 13 14
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
The documentation shows BigQuery as a source that pulls conversion data on a schedule — hourly polling, merged daily — with warehouse metrics displayed as KPIs on the results pages, plus two-way data warehouse sync, a CDP connection, and an authenticated, paginated API for exporting segments. Warehouse-native measurement is how I re-check a result in our own data; we found no public information on visitor-level raw data export or an API for managing experiments with stated limits. 1 6 5 5
The E-Commerce Manager
The BigQuery integration is documented in working detail: goals pull conversion data from the warehouse on a schedule, with hourly polling, a daily merge and a required visitor identifier and timestamp, and warehouse metrics can be displayed as KPIs on results pages, so I can check a test against my own numbers. Connections to any CDP, two-way data warehouse sync, heatmapping and analytics integrations, and a documented segment-export API with bearer authentication round it out. It sits below the top level because the warehouse piece is a premium add-on behind the customer success manager and I found no public information on visitor-level raw data export or stated API limits. 1 2 6 5
The Product Engineer
This is the part I care about most and it is genuinely there: goals can pull conversion data from BigQuery on a schedule — hourly polling, daily merge — and BigQuery metrics can be displayed as KPIs on the results pages, with the vendor also claiming two-way sync to target and analyse with warehouse data. A documented segment-export endpoint with bearer authentication and pagination exists, alongside CDP and heatmap/analytics integrations. The warehouse path is a premium add-on you must ask a customer success manager about, and I found no public information on raw visitor-level export or streaming out. 1 6 5 5
The CRO Consultant
Strong for my practice: two-way sync with a data warehouse, BigQuery goals that pull conversion data on a schedule so results are measured on the client's own data, a documented API endpoint with bearer authentication, and CDP plus analytics integrations. It stops short of the top tier because warehouse integrations are a premium add-on behind a customer-success conversation, and no rate limits or visitor-level export-out flow appear on the captured pages. 1 6 5 5
The Data Protection Officer
Segments are exportable through a documented API with bearer authentication and pagination, BigQuery can act as a source that pulls conversion data on a schedule and displays warehouse metrics on results pages, and the homepage offers CDP connection and two-way sync with a data warehouse. Visitor-level export out of the platform and stated API limits are not evidenced in the captured pages, and the warehouse integrations come as a premium add-on. 1 6 5
The Skeptic
The BigQuery integration is documented with working detail — goals pulling conversion data on a schedule, hourly polling with a daily merge, required query columns, warehouse metrics displayed as KPIs — and the API reference documents a segment export endpoint with bearer authentication, pagination and filtering. Against that, the analytics and heatmapping integrations are unnamed beyond "top tools", the data warehouse capability is a premium add-on priced only by contacting the vendor, and we found no public information on visitor-level raw export or an API for managing experiments with stated limits. 1 5 6 5
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
Contracting sits with a French simplified joint stock company under French law, and the privacy policy states that personal data is stored on servers in the European Union. The pricing page, though, presents data residency as "EU or US" — Enterprise "EU or US or Custom" — with no default region stated, and we found no public information on a data processing agreement or a published subprocessor list covering the visitor data the script collects. 2 3 4
The E-Commerce Manager
The contracting entity is Kameleoon SAS in Paris, governed by French law with a CNIL declaration and Commercial Court of Paris jurisdiction, the vendor's site runs at Hetzner in Germany, and the privacy policy states personal data of website users is stored in the EU. The pricing page, though, offers "Data residency EU or US" — an option rather than a stated default — so EU processing of my visitors' behaviour data is not confirmed as standard. I found no public information on a data processing agreement or a published subprocessor list with locations. 2 3 4
The Product Engineer
The contracting entity is Kameleoon SAS in Paris under French law with a CNIL declaration, the privacy policy states that personal data is stored on servers in the European Union, and a German host (Hetzner Online GmbH, Gunzenhausen) is named in the legal notice. The plans page, however, offers data residency of 'EU or US' — 'EU or US or Custom' on Enterprise — so EU-by-default is not established for customer data, and I found no public information on a data processing agreement or a subprocessor list with locations. 2 3 4
The CRO Consultant
A French contracting entity, French law, a CNIL declaration and a named German hosting provider (Hetzner) are published. However, the plans page presents "Data residency EU or US" (Enterprise: "EU or US or Custom"), so EU processing is not evidenced as the default for visitor data, and we found no public information on a data processing agreement or a subprocessor list. 2 3 4
The Data Protection Officer
The contracting entity is a French simplified joint stock company in Paris under French law, the privacy policy states personal data is stored on servers within the European Union, and the legal notice names a German hosting provider. The captured pages give different figures for residency — the pricing page offers data residency EU or US with no default region stated — and we found no published subprocessor list including the snippet CDN and no data processing agreement in the captured pages. 2 3 4
The Skeptic
The contracting entity is solidly European — Kameleoon SAS in Paris, French law, the Commercial Court of Paris, with Hetzner in Germany named as host — and the privacy policy states that personal data is stored on servers in the European Union. The captured pages give different pictures of residency, though: the pricing page offers a choice of EU or US with no default stated, and we found no public information on a data processing agreement, a platform subprocessor list with locations, or where the test snippet is delivered from. 2 3 4
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
The plans page publishes a free 30-day trial with no credit card required and up to 3 experiments, and a Starter tier capped at 10 experiments and 50,000 visitors per month — but no monetary figure appears anywhere: Enterprise is "Custom" and data warehouse integrations are a premium add-on to discuss with a Customer Success Manager. For a product priced on traffic, I cannot compute an annual cost from the public pages. 1 2 5 5
The E-Commerce Manager
Public and concrete: a free 30-day trial with no credit card required and up to 3 experiments, a Starter tier to "Build up to 10 experiments and test 50,000 visitors per month", and an Enterprise tier priced "Custom" with unlimited experiments and unlimited tested traffic. I found no public price figures for any paid tier, every add-on from Personalization to CUPED is listed without a price, and data warehouse integrations are "available as a premium add-on" where I should "Contact your Customer Success Manager" — so I cannot estimate what my December traffic would cost. 2 5
The Product Engineer
The captured plans page gives structure without money: a free 30-day trial capped at 3 experiments, a Starter tier bounded at 50,000 visitors per month and 10 experiments, an add-on list, and a custom-priced Enterprise tier. No price figure for any paid tier appears on the captured pages, and the data warehouse integration is explicitly available by contacting your Customer Success Manager, so a real annual cost cannot be computed from public pages. 2 5
The CRO Consultant
The traffic metric is stated — "50,000 visitors per month" with up to 10 experiments on the entry tier, plus a free 30-day trial with three experiments — so I can size volume before signing. But no price figure is published for any paid tier or module: Enterprise is "Custom" and data warehouse integrations are a premium add-on where you "Contact your Customer Success Manager", so the real annual cost is not computable from public pages. 2 5 5
The Data Protection Officer
The plans page states a free 30-day trial of Prompt-Based Experimentation and a Starter tier of up to 10 experiments and 50,000 tested visitors per month, with Enterprise priced as custom and modules such as personalisation, CUPED and mobile app testing listed as extras. No price figures or billing periods appear in the captured pages, and the data warehouse integration is stated as "Contact your Customer Success Manager". 2 5
The Skeptic
The captured pricing pages show a free 30-day trial and a Starter tier with its traffic metric stated — up to 10 experiments and 50,000 visitors per month — but no price figure for any tier appears anywhere. Enterprise is custom, every add-on from personalisation to CUPED carries no price, and the data warehouse integration says "Contact your Customer Success Manager", so a buyer cannot compute an annual cost from these pages. 1 2 5
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in FR | 2/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?The privacy policy statement covers personal data of website users, and the pricing page offers "Data residency EU or US" (Enterprise: "EU or US or Custom"), so customer data may be hosted outside the EU and no default region is stated. |
2/4 pts | 3 Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Kameleoon
Is Kameleoon European?
Yes. whats-best.ai classifies Kameleoon as EU-Made. Its vendor, Kameleoon SAS, is incorporated in France, per the vendor’s page captured 16 Nov 2026.
Where does Kameleoon store data?
Kameleoon stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.
Does Kameleoon have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Kameleoon?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Kameleoon alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The privacy policy statement covers personal data of website users, and the pricing page offers "Data residency EU or US" (Enterprise: "EU or US or Custom"), so customer data may be hosted outside the EU and no default region is stated.
- Weak sourcing — Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 39 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- We read 6 of the 14 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.kameleoon.com Checked 16 Nov 2026 Details →
- 2 Pricing page www.kameleoon.com Checked 16 Nov 2026 Details →
- 3 Privacy policy www.kameleoon.com Checked 16 Nov 2026 Details →
- 4 Legal notice www.kameleoon.com Checked 16 Nov 2026 Details →
- 5 Analytics, data export & integrations — found from sitemap docs.kameleoon.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Oct 2026 Details →
- 6 Analytics, data export & integrations — found from sitemap docs.kameleoon.com Checked 16 Nov 2026 Details →
- 7 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 8 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 9 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 10 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 11 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 12 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 13 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →
- 14 Structured-data backfill: markup only, no text or screenshot docs.kameleoon.com Checked 8 Nov 2026 Details →