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 Skeptic
The captured pages show client-side A/B and A/B/n tests, split-URL and multivariate testing, a visual editor and a code editor, and rule-based personalisation across forty-plus targeting parameters including behaviour, device and geolocation. We found no public information on a server-side SDK, feature flags or holdouts, and the vendor's own answer on running multiple experiments tells customers to watch segmentation and traffic allocation so their experiments do not influence each other's results. No documented experiment lifecycle or searchable library of past results appears in these captures. 1 2 5 6