Kameleoon vs Optimizely

Kameleoon

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.

Optimizely

The plans page lists A/B, multi-page, feature and server-side testing with real-time personalisation and audience targeting, which is more than client-side splits. But every claim sits on a feature grid: I found no public information on documented SDKs, multivariate tests, mutually exclusive groups or holdouts, so the delivery mechanics cannot be verified from what was captured.

Kameleoon

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.

Optimizely

The whole statistical story is one phrase on the plans page — "Proprietary Stats Engine for results you can trust" — a brand name where I need a method, and neither frequentist nor Bayesian is stated. I found no public information on sample-size or duration guidance, protection against peeking, corrections for multiple metrics or variants, or sample ratio mismatch detection.

Kameleoon

The only captured statements about cookies concern Kameleoon's own marketing site — purposes, an opt-out, an Adroll retargeting cookie — and we found no public information on when the testing script runs relative to consent, what it stores on a visitor's device, or any consent-pending or cookieless mode. A "Data Privacy & Security" module name on the homepage is not documentation of the script's behaviour.

Optimizely

The vendor's consent documentation is thorough about the customer's obligations — consent freely given, per purpose, affirmative, stored and tracked against its purpose and data — which places the consent burden squarely on the operator. On the script itself I found no public information: nothing captured says what it stores on a device, whether it runs before consent, whether a cookieless mode exists, or how visitor identifiers are treated beyond a hashed identifier that may be shared with named social networks.

Kameleoon

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.

Optimizely

I found no public information on snippet size, loading behaviour, flicker handling or Core Web Vitals impact on any captured page, including the homepage and plans page where such figures would sit. With no published measurement of any kind, this lands at the bottom of the scale.

Kameleoon

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.

Optimizely

Warehouse connections to BigQuery, Snowflake, Redshift and Databricks are documented with real setup detail — service accounts, custom roles, permissions — and the plans page claims warehouse-native analytics. But the documented direction is the customer's warehouse feeding Optimizely Analytics; I found no public information on a documented API, export of results, or visitor-level data leaving the platform for independent re-analysis, which is the direction that makes a result checkable.

Kameleoon

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.

Optimizely

The contracting entity varies by deal — Optimizely North America Inc., Optimizely AB, or Optimizely GmbH in Berlin — and nothing captured states where visitor data is hosted or processed. Subprocessors appear only as broad categories, the stated safeguard for transfers is the EU-US Data Privacy Framework, and a hashed user identifier may be shared with US-based networks such as Google and Facebook; a data processing agreement exists, but residency remains an open question.

Kameleoon

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.

Optimizely

Every plan is "individually packaged" through a conversation, so no tier, traffic metric or limit is public and no annual invoice can be computed. The published terms do state pricing mechanics — overage at "two times (2x) Usage Volume unit price" invoiced monthly in arrears, automatic twelve-month renewal, ninety days' notice to cancel, no usage reduction during a term — but mechanics without prices still leave the cost unknowable.