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.
The Data Protection Officer
The vendor's own pages show no-code client-side testing — new variants in two clicks — plus a written experimentation framework with a hypothesis template and a one-week minimum run. We found no public information on the vendor's own server-side delivery, SDKs, feature experiments or multivariate tests; the server-side and feature-flag capabilities named on the A/B testing page belong to third-party tools it compares, and delivery beyond the client-side path rests on integrating external testing platforms. 2 3 8