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 Growth Lead
The A/B testing pages show client-side testing of messages and visuals with AI-generated experiences, control of the visitor percentage exposed, a 50/50 start rising to 95% personalised traffic with a 5% background control group, and real-time intent-based personalisation like adaptive CTAs, dynamic product highlights and exit-intent actions. We found no public information on server-side or SDK delivery, multivariate or multi-page tests, or feature-flag experiments, so a programme would live on the website only — though the behavioural targeting behind the personalisation does go well beyond URL rules. 3 4 5