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 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, 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 Product Engineer
A/B testing inside a no-code editor, behavioural segmentation, rule-based targeting and placements-based personalisation are all documented, and Workspaces lets marketers preview tests on production in three clicks — that is the anchor-5 package without the split-URL or multivariate pieces. What I care about is absent from the evidence: I found no public information on server-side experiments through documented SDKs, feature flags, mutual exclusion or holdouts, and the API the terms define is for wiring your applications into the platform, not for running experiments server-side or at the edge. 1 5 6 3