Product review
Unbounce review
Unbounce is a landing page builder with genuine testing behind it. For research teams the deciding question is not features — it is whether you need the tier that unlocks A/B testing, and whether you have the traffic to use it.
Written and maintained by CASRAI Editorial Board
Last updated
Unbounce — worth it from the Build tier; Experiment if you will really test
From $29/mo ($22 billed annually)
The value for a research team is publishing independence — pages that live outside your institutional CMS and can be changed without a central web team ticket. Build at $99/month ($74 annually) gives unlimited pages and AI copywriting, which covers that. Only step up to Experiment at $149/month ($112 annually) if you genuinely have the traffic to run A/B tests; below a few hundred conversions per variant, testing produces false confidence rather than answers.
Most research pages do not have enough traffic to test meaningfully. Knowing that before you buy saves $50/month.
At a glance
Unbounce plans
Verified from the vendor pricing page, 18 August 2026. Annual price in brackets.
| Dimension | Starter | Build | Experiment | Optimize |
|---|---|---|---|---|
| Price / month | $29 ($22) | $99 ($74) | $149 ($112) | $249 ($187) |
| Pages | 5 | Unlimited | Unlimited | Unlimited |
| Traffic volume | Up to 500 | Up to 20,000 | Up to 30,000 | Up to 50,000 |
| Users | 1 | 1 | 3 | 5 |
| Root domains | 1 | 1 | 2 | 3 |
| A/B testing | No | No | Unlimited | Yes |
| AI copywriting | No | Yes | Yes | Yes |
| Smart Traffic | No | No | No | Yes |
Annual billing is 25% cheaper across the published tiers. Concierge and Agency are custom-priced, starting at 100,000 and 50,000 traffic volume respectively.
The real value
What research teams actually buy this for
The feature list is beside the point for most institutional buyers. What Unbounce sells a research team is publishing independence.
Institutional web estates are managed centrally for entirely good reasons — brand consistency, accessibility compliance, security. The consequence is that changing a page means raising a ticket, waiting in a queue, and accepting a template that was designed for a different purpose. On a recruitment campaign with a deadline, that queue is fatal: by the time the page is live the advertising has already run against the old one.
A standalone builder puts the page under the control of the team that owns the outcome. It also sidesteps the second institutional problem, which is that heavy CMS templates load slowly and abandonment rises sharply with load time.
The applications that follow are all the same shape: clinical trial and study recruitment, cohort follow-up for longitudinal studies, event and training registration, survey and panel recruitment, and core facility access pages. Each needs to be published quickly, changed often, and measured — and none of them fit comfortably in a departmental CMS.
The decision
Which tier you actually need
Starter ($29/mo) is limited to five pages and 500 visitors. That traffic ceiling is low enough to be a real constraint on anything with advertising behind it, and there is no AI copywriting. Reasonable for a single standing page; not for a campaign.
Build ($99/mo, $74 annually) is where most research teams should land. Unlimited pages and 20,000 traffic covers a recruitment campaign comfortably, and unlimited pages means a page per study, per site or per audience segment — which matters, because a targeted page consistently outperforms one generic page for everything.
Experiment ($149/mo, $112 annually) adds unlimited A/B testing and lifts you to three users and two domains. Buy this only if you will actually test. The honest arithmetic is unforgiving: detecting a change from a 10% to a 12% conversion rate at conventional power needs roughly several thousand visitors per variant, and a recruitment page seeing 200 visits a month cannot run that test. The extra $50 a month buys a feature you will not be able to use.
Optimize ($249/mo, $187 annually) adds Smart Traffic, which routes visitors to whichever variant historically converts best for people like them rather than splitting evenly. It is genuinely useful at lower volumes than classical A/B testing needs, because it optimises continuously instead of waiting for significance — but it gives you a better outcome rather than a finding you can publish or transfer. If you want to know why something worked, that is still a designed test.
The multi-user consideration is worth flagging: Build includes one user. A team where a coordinator drafts and a comms lead reviews needs Experiment for the seats, regardless of testing.
Honest assessment
Trade-offs and institutional friction
Cost against institutional alternatives. $99 a month is trivial next to a recruitment budget and awkward against a departmental discretionary spend. It is also a recurring subscription, which some institutions handle badly on grant funding — check that a monthly card payment is acceptable before committing, because a purchase-order-only finance office can make this genuinely difficult.
Accessibility is your responsibility. A standalone builder means you have stepped outside whatever accessibility review your institutional CMS applies. Public-sector bodies in the UK and EU have legal accessibility obligations, and US institutions have Section 508 and ADA exposure. Check contrast, keyboard navigation, form labelling and heading structure yourself, and get the page reviewed if you have someone who does that.
Brand governance. Publishing independence cuts both ways. Agree with your comms team what may sit on a non-institutional domain before you build, rather than after someone notices.
Traffic overage. Tiers are capped by visitor volume, and a campaign that succeeds harder than expected pushes you over. Watch it during an active push.
Ethics approval still applies. If the page is a recruitment material for a study, its copy is generally part of what your IRB approved. Changing it — including for testing — usually needs an amendment. That constraint is a genuine reason many research teams should stay on Build rather than Experiment.
Ready to move
Start with the tier that fixes your actual bottleneck
For most research teams that is publishing independence rather than experimentation — Build at $74/month billed annually. Move up to Experiment only when you have the traffic to make a test mean something.
From $29/mo ($22 billed annually)
Try Unbounce →Opens on the vendor's site · CASRAI referral linkFrequently asked questions
Common questions
- How much does Unbounce cost?
- Starter $29/month, Build $99/month, Experiment $149/month and Optimize $249/month, with 25% off for annual billing ($22, $74, $112 and $187 respectively). Concierge and Agency tiers are custom-priced. Verified 18 August 2026.
- Which Unbounce plan includes A/B testing?
- Experiment at $149/month ($112 annually) is the first tier with A/B testing, and it is unlimited there. Starter and Build do not include it, which surprises people who bought Build expecting to test.
- What is Smart Traffic?
- An AI feature on the Optimize tier that routes each visitor to whichever page variant has historically converted best for visitors like them, rather than splitting traffic evenly. It works at lower volumes than classical A/B testing because it optimises continuously — but it gives you a better outcome rather than a transferable finding.
- Is Unbounce worth it for a research team?
- If your bottleneck is being unable to publish or change a page without a central web team ticket, yes — that is what it fixes, and Build at $74/month billed annually is usually the right tier. If you only need one page that rarely changes, an institutional page is cheaper.
- Do we need the Experiment tier to A/B test recruitment pages?
- You need it for the feature, but check first whether you have the traffic. Detecting a realistic conversion improvement needs roughly several thousand visitors per variant, and most study recruitment pages do not see that. There is also an ethics constraint — recruitment copy is usually part of what your IRB approved, so testing variants generally needs an amendment.
- What about accessibility on a standalone landing page?
- It becomes your responsibility, because you have stepped outside your institutional CMS review. UK and EU public bodies have legal accessibility obligations and US institutions have Section 508 and ADA exposure. Check contrast, keyboard navigation, form labelling and heading structure before publishing.
Going deeper
