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 Growth Lead
Split testing is documented and real: Clerk.js divides visitors evenly across any number of variants of the store's own content blocks and you compare them by label in the Analytics page, next to a well-documented personalisation engine for search, recommendations and email. But tests are configured through a data attribute in the embed code rather than a visual editor my marketers could drive alone, and we found no public information on targeting by URL, device or audience for tests, on multivariate testing, or on server-side experiments. For my programme this is a specialist's personalisation tool, not a team-wide testing platform. 5 7