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
Split testing is documented, but only for this vendor's own content blocks: variants are declared in the embed code with a data-split-test attribute, the client script splits visitors evenly across any number of variants, and results are compared by label in the analytics page. That is a client-side A/B mechanism attached to a personalisation engine — we found no public information on multivariate tests, holdouts, mutually exclusive experiment groups, or allocating experiments from a server-side SDK. If I can only test which of the vendor's own recommendation logics wins, I still need a real experimentation platform next to it. 5 7