whats-best.ai
Search Sign in

Conversion Optimization

Kameleoon

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 4 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? →

Read this page as one judge. Each weighs the same scores by what they care about.

The Skeptic

Weighted verdict

A statistician who has watched too many "winners" regress to zero. Reads for the method by name, what stops a team from peeking, sample ratio mismatch checks and multiple-comparison corrections — and treats a "probability to beat" without documented assumptions as marketing.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Skeptic

Experiment types & delivery

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 — Simple A/B split of one page element through a visual editor; no server-side option, no targeting beyond URL.

3 — Client-side A/B and split-URL tests with basic audience targeting, and no SDK or server-side delivery.

5 — Client-side and server-side experiments through documented SDKs for common languages, multivariate and multi-page tests, audience targeting on behaviour and attributes, and rule-based personalisation.

8 — Feature-flag-based experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, edge or CDN delivery, 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.

Report an error

The Skeptic

Feature-flag experiments, mutually exclusive groups with holdouts, multivariate and mobile testing, and personalisation all appear on the captured pages, alongside graphic, code and SDK variation editors. What holds me back is that this is homepage and plans-page grids rather than documentation: we found no public information on edge or CDN delivery, a documented experiment lifecycle, or a searchable library of past results, and the SDKs are named in a legal notice rather than documented. 1 2 4

Report an error

Statistical method & guardrails

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 — A "winner" or "probability to beat" figure with no documented method, no stated sample-size guidance and no warning against stopping early.

3 — The method is named (frequentist or Bayesian) but its assumptions are not documented, and nothing prevents a test from being called while it is still underpowered.

5 — Documented method with confidence or credible intervals, a sample-size or test-duration calculator, and stated guidance on when a result may be read.

8 — Sequential testing or an equivalent documented protection against peeking, 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.

Report an error

The Skeptic

The right guardrails are named — sequential testing, multiple testing correction, SRM detection, CUPED, bandits — but every one appears as a feature bullet or a one-line claim, with no stated method, no assumptions, no intervals, no sample-size calculator and no guidance on when a result may be read. Until the assumptions behind the sequential test are written down, I treat the guardrail list as intent, not method. 1 2

Report an error

Snippet performance & flicker

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 snippet with no stated size, no flicker handling and no mention of performance.

3 — An anti-flicker snippet that hides the page until the test loads, with a timeout, and no published figures for script size or load cost.

5 — Script size and loading behaviour documented, asynchronous loading option, flicker handling explained with its trade-off, and CDN delivery of the snippet.

8 — Published performance figures including 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.

Report an error

The Skeptic

One figure is published — a snippet that loads under 70 ms, alongside 99.99% uptime — with no measurement conditions, script size, loading behaviour or flicker handling anywhere in the captures. A load-time claim without methodology tells me nothing about what it costs a real page. 2

Report an error

Analytics, data export & integrations

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 — Results visible in the vendor's dashboard only; no export, no analytics integration, no API.

3 — CSV export of aggregated results and one analytics integration, with no visitor-level data and no documented API.

5 — Integrations with common analytics and tag managers, export of results, and a documented API for managing experiments and reading results.

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

Report an error

The Skeptic

The API is documented with authentication and pagination, and the warehouse story looks real: two-way sync plus BigQuery metrics and goals feeding the results pages means an experiment can be measured on the customer's own data. But we found no public information on visitor-level raw data export or stated API limits, and the warehouse capability sits behind an unpriced premium add-on. 1 5 6

Report an error

European sovereignty

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 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and visitor data leaving the EU without a stated safeguard.

3 — EU data residency offered as an option or an enterprise add-on while the contracting entity is non-EU, or the subprocessor list is absent.

5 — EU processing of visitor data as standard and an EU contracting entity, but parts of the chain — CDN, support access, analytics — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure including the delivery of the snippet, EU contracting entity, subprocessor list published, and a DPA 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.

Report an error

The Skeptic

The contracting entity is French, disputes go to the Commercial Court of Paris, storage is stated to be in the EU on named German infrastructure, and there is a CNIL declaration number. We found no public information on a subprocessor list, a DPA covering the visitor data the script collects, or where the snippet itself is delivered from. 3 4

Report an error

Pricing transparency not rated — the vendor publishes no price

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 starting price or a free tier exists, but the traffic metric, the limits and what happens above them are unstated — the invoice is unknowable.

5 — Tier prices public with the traffic metric and its limits defined, but at least one commonly needed piece (server-side SDKs, personalisation, overage) is unpriced or "contact sales".

8 — Every tier priced publicly with the traffic metric defined, limits, overage rates, module prices, 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.

Report an error

The Skeptic

A free 30-day trial limited to three experiments exists, but every paid tier is "custom", the add-on list is unpriced, and the data warehouse module is explicitly "Contact your Customer Success Manager". The traffic metric — "tested traffic" — appears without limits or definitions, so a real annual invoice cannot be computed from the captured pages. 2 5

Report an error

European sovereignty — proven facts

1 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined ⚠ unverified — uncited Report an error
Subprocessors Not determined ⚠ unverified — uncited Report an error

Where this could be wrong

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.

Do you know more about Kameleoon? Tell us Report an error on this page

Sources (6)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.kameleoon.com Checked 22 Sep 2026 Details →
  2. 2 Pricing page www.kameleoon.com Checked 22 Sep 2026 Details →
  3. 3 Privacy policy www.kameleoon.com Checked 22 Sep 2026 Details →
  4. 4 Legal notice www.kameleoon.com Checked 22 Sep 2026 Details →
  5. 5 Analytics, data export & integrations — found from sitemap docs.kameleoon.com Checked 1 Oct 2026 Details →
  6. 6 Analytics, data export & integrations — found from sitemap docs.kameleoon.com Checked 1 Oct 2026 Details →