abtestly vs Convert: an honest comparison
abtestly and Convert are both code-friendly A/B testing tools, and the honest answer is that they fit different teams. Convert is the more mature and the broader of the two: a visual editor, 90+ integrations, multivariate and full-stack testing, and a decade of operating history. abtestly is leaner and edge-native: code-first JSON experiments in version control, Cloudflare-edge delivery, a fully published statistics methodology, and a permanent free plan, at a lower price for the same traffic. Pick Convert for breadth and maturity; pick abtestly for a fast, code-first workflow on a tighter budget.
I build A/B tests on both of these tools, so the comparison below is from real use, not a spec sheet. Convert pricing was checked on convert.com on 10 June 2026; check their site for current numbers.
At a glance
| dimension | abtestly | convert |
|---|---|---|
| Entry paid price (100K MTU) | Pro $179/mo, or $143/mo annually; Starter $79/mo (25K MTU) | Growth $399/mo, or $299/mo annually; Pro higher again |
| Free option | Permanent free plan: 1 experiment, 3K MTU | 15-day trial (no card) |
| Editor | Code / JSON only, no visual editor | Visual editor plus five code editors |
| Test types | A/B testing | A/B, split URL, multivariate, full-stack and feature flags (Pro) |
| Delivery | Cloudflare edge, 300+ cities; config served without an origin round-trip | Akamai CDN; synchronous by default |
| Snippet and anti-flicker | ~10KB gzipped runtime, scoped hide, no-flicker first paint | Built-in anti-flicker shield, synchronous by default |
| SPA route changes | Per-site SPA mode; lifecycle re-runs cleanup-first on route change | Re-evaluates on history.pushState; you undo your own DOM changes |
| Stats engine | Two-proportion z-test, 95% CI on every lift, fixed-horizon (sequential on roadmap) | Frequentist and Bayesian; sequential testing on Pro |
| Published methodology | Fully documented, including SRM and verdict thresholds | Feature docs exist; no single published methodology page found |
| Code in version control | Native: experiments are JSON, diffable and reviewable | REST API, a version-control widget, and an MCP server |
| Integrations | Native GA4 | 90+ integrations |
| Beyond A/B testing | Not yet | Heatmaps and personalization |
| Compliance posture | GDPR-conscious; no published certifications yet | ISO 27001, SOC 2 Type 2, EU servers |
| Overage handling | No overage charges; new visitors stop being bucketed | Optional overage billing per block |
Where Convert is genuinely better
Convert is the more complete platform, and it is fair to say so plainly. It has a visual editor that a marketer can drive without a developer, where abtestly has nothing comparable because its experiments are code and JSON. It does multivariate, split URL, and full-stack testing with feature flags, where abtestly does A/B testing. It carries 90+ one-tag integrations against abtestly's single native GA4 connection, offers sequential testing today where abtestly runs fixed-horizon tests, and bundles heatmaps and personalization. It also brings published ISO 27001 and SOC 2 certifications, EU servers, phone support on Pro, and a decade-plus of operating history. If breadth, a visual editor, or formal compliance decide it for you, Convert wins.
Where abtestly is better
abtestly trades that breadth for speed, transparency, and price. Experiments are JSON, so they version-control, diff, and review like the rest of your code, with no editor state living outside your repo. The test config is served from Cloudflare's edge in 300+ cities with no origin round-trip, behind a scoped anti-flicker hide and a roughly 10KB gzipped runtime. The entire statistics methodology, including the confidence-interval math, the sample-ratio-mismatch check, and the verdict thresholds, is published, and nothing is called a winner below 95% confidence. There is a permanent free plan rather than a trial, no overage charges, and at the same 100K tested users it runs about half the price of Convert Growth.
Pricing, like for like
At the same 100K monthly tested users, abtestly Pro is $179/mo, or $143/mo billed annually, against Convert Growth's $399/mo, or $299/mo annually, so roughly half the price. Convert Growth caps active experiences at 5 per project, so the closest match on capability is Convert Pro, which is higher again. abtestly starts lower too, with a $79/mo Starter tier at 25K MTU and a permanent free plan at 3K MTU, where Convert offers a 15-day trial. abtestly never charges overage; new visitors simply stop being bucketed once you hit your limit. Convert's overage billing is optional but bills per block when left on.
The developer workflow
This is the difference you feel day to day. On abtestly an experiment is JSON: you write raw JavaScript and CSS per variant, commit it, and review it like any other change. SPA mode re-runs the lifecycle cleanup-first on route changes, so a variation does not leak across virtual pages. Convert gives you five code editors, from project scope down to variation scope, plus a visual editor and a REST API, a version-control widget, and an MCP server, so it is genuinely code-friendly too, just with more surface area and a visual path as the default. If your team lives in a repo and a CI pipeline, abtestly's JSON-first model fits more naturally. If your team mixes developers and marketers, Convert's visual editor earns its place.
Whichever you choose, the parts that actually break a client-side test are the same. I cover them in why experiments stop firing on SPA route changes and stopping flicker without tanking Core Web Vitals.
Which should you pick
Pick Convert if you need a visual editor for non-developers, multivariate or full-stack testing, a wide integration stack, heatmaps and personalization, or formal compliance certifications, and the budget that comes with a mature platform.
Pick abtestly if your experiments are built by people who write code, you want edge delivery and a JSON workflow in version control, you report into GA4, and you would rather start on a free plan and read a published statistics methodology than pay for breadth you will not use.
Genuinely unsure? Run both for a week, abtestly on its free plan and Convert on its trial, and compare visitor counts, conversion rates, and the sample-ratio-mismatch check before you commit.
Common questions
Is abtestly or Convert cheaper?
abtestly is cheaper at the same volume. At 100K monthly tested users, abtestly Pro is $179/mo, or $143/mo billed annually, against Convert Growth at $399/mo, or $299/mo annually. abtestly also has a permanent free plan and no overage charges, where Convert offers a 15-day trial and optional overage billing. Convert Growth caps active experiences at 5 per project, so the closest match on capability is Convert Pro, which is higher again.
Which is better for developers, abtestly or Convert?
Both are code-friendly, but they lean different ways. abtestly is code-first: experiments are JSON in version control, delivered from Cloudflare's edge, with a fully published statistics methodology. Convert gives you five code editors plus a visual editor, 90+ integrations, multivariate and full-stack testing, and a longer operating history. Pick abtestly for a lean, edge-native, version-controlled workflow; pick Convert for breadth, a visual editor, and a mature ecosystem.
What does Convert do that abtestly does not?
A visual editor a marketer can drive, multivariate and full-stack testing with feature flags, 90+ integrations, sequential testing today, heatmaps and personalization, published ISO 27001 and SOC 2 certifications with EU servers, and a decade-plus of operating history. abtestly is code-first A/B testing; multivariate, sequential testing, and formal certifications are not in the product today.
What does abtestly do that Convert does not?
A permanent free plan instead of a trial, no overage charges, a fully published statistics methodology with a 95% confidence interval on every lift and an SRM check, a code-first JSON workflow that lives in version control, edge delivery from 300+ Cloudflare cities with a roughly 10KB gzipped snippet, and a lower price at the same tested-user volume.
Can I try both before committing?
Yes. Run the same test in both tools at once for a week, abtestly on its free plan and Convert on its trial, then compare visitor counts, conversion rates, and the sample-ratio-mismatch check before you commit to either.