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
The pricing pages sell 'A/B testing & outcomes analysis' as an add-on, and the vendor's experiment guide defines A/B, split, multivariate and funnel testing — but the product-facing line in that guide is about monitoring A/B tests run in AB Tasty, Omniconvert or Optimizely. We found no public information on a visual editor, on how traffic is split, on audience targeting beyond the URL, or on server-side delivery. For a team that needs to build tests without a developer, the captured pages document a testing add-on plus third-party monitoring, not a delivery editor. 7 2 2