Best CRO Tools for a Real Testing Stack
The CRO tools that actually matter, grouped by what each one is for — testing, session replay, feedback and analytics — with honest cost ranges.
The CRO tools that matter fall into four categories: a testing platform to run experiments, a session replay or heatmap tool to see where visitors get stuck, a feedback tool to ask them directly, and an analytics platform to measure the funnel underneath it all.
Most teams over-invest in the first category and under-invest in the other three. This list covers all four, and assumes you already understand what A/B testing is for before you shop for software to run it.
On this page
What does a CRO tool stack actually need to cover?
Four distinct jobs, and no single tool does all four well. Testing tools split traffic and measure results. Session replay and heatmap tools show you where attention and hesitation actually happen. Survey and feedback tools ask visitors directly, which behavior data alone can't do. Analytics platforms measure the funnel those first three tools are trying to improve.
The mistake most teams make is buying the testing tool first and stopping there. A testing platform tells you whether a change worked; it does nothing to tell you what to change in the first place. Without at least one of the other three categories, a team is stuck generating test ideas from opinion instead of from evidence, which is the single biggest predictor of a testing program that runs a lot of tests and learns very little.
This is also the order most vendors would rather you didn't think about, because the testing platform is the highest-priced line item in the stack and the one every vendor in that category is competing hardest to sell you. Nobody pitches you on adding a cheap survey widget; every sales call pitches the platform with the biggest number attached. Buying in the order your team actually needs, not the order that gets pitched hardest, is most of what separates a stack that gets used from one that doesn't.
Which A/B testing platform should anchor the stack?
Whichever one matches your traffic and your team's technical depth — we cover that choice in detail in our testing tools guide, including the trade-off between hosted platforms and self-hosted, developer-first ones like GrowthBook [1] and Statsig [2]. That comparison holds regardless of which other three categories you add around it.
95% chance to win
What matters for this list is not re-litigating that choice, but being clear that the testing platform is one piece of four, not the whole stack. A team that spends a full quarter evaluating testing platforms and none evaluating a session replay tool has optimized the wrong decision.
If you're not sure which platform fits, default to whichever one your team is most likely to actually configure correctly and check every week, not the one with the longest feature list on its pricing page. A mid-tier platform used consistently produces more usable results over a year than a best-in-class platform that gets set up once and then ignored while everyone waits for someone else to check the dashboard.
Which heatmap and session replay tool is worth adding?
Whichever one your team will actually watch. Hotjar and Crazy Egg both cover the category well, with heatmaps for aggregate attention patterns and session recordings for watching individual visitors hit a specific friction point [3][4]. The tool matters less here than the habit — a heatmap nobody reviews is a subscription, not a CRO tool.
Set a standing habit before you set up the tool: one hour a week, watching five to ten sessions on whichever page currently has the steepest drop-off. That habit produces more usable test ideas over a quarter than an occasional deep dive after a bad month does, because it catches friction while it's still small enough to fix in a single test rather than after it's already cost a quarter of lost conversions.
| Category | What it answers | Example tools |
|---|---|---|
| A/B testing | Did the change actually work? | VWO, Optimizely, GrowthBook, Statsig |
| Session replay / heatmaps | Where do visitors hesitate or get stuck? | Hotjar, Crazy Egg |
| Surveys / feedback | Why did they hesitate, in their own words? | On-site survey widgets, exit-intent polls |
| Analytics / funnel | Where exactly in the funnel is the drop happening? | Amplitude, product analytics platforms |
Do you need a dedicated survey or feedback tool?
Eventually, yes, once behavior data alone stops answering your questions. Replay and heatmap tools show you that visitors abandon a form at a specific field; they don't tell you why. A simple on-page survey — one question, triggered at the right moment — closes that gap for a fraction of the cost of a full research study.
Amplitude and similar product analytics platforms increasingly bundle lightweight testing and survey features alongside their core funnel reporting, which is worth checking before adding a fully separate tool for a team already paying for one of these platforms [5]. Check what's already included in a tool you're paying for before adding a new line item to answer a question the existing one might already cover — it's a five-minute check against a recurring bill.
How much does a full CRO stack cost, realistically?
Less than most teams assume once you skip the categories you don't need yet. A small team can run a testing tool, a session replay tool, and free or low-cost survey widgets for well under what a single enterprise testing platform license costs alone. The spend curve is steep at the high end — enterprise testing, dedicated research panels, a full analytics suite — but the entry point for all four categories combined is modest.
Start with testing and replay only
These two cover the most common gap: knowing whether a change worked and having a source of new ideas.
Add a survey tool once you have a specific question
Not before. A survey without a question worth asking collects noise.
Add dedicated analytics only if your current setup can't answer a funnel question
Many teams already have enough analytics and are missing a different category entirely.
Review usage, not just cost, once a year
A cheap tool nobody opens is worse value than an expensive one the team uses every week.
How do you know when you've outgrown your current stack?
When the same question keeps coming up and none of your tools can answer it. If every retro ends with "we don't actually know why that test lost," that's a feedback-tool gap, not a testing-tool problem. If tests keep launching later than planned because nobody agrees on what to test next, that's an ideas gap a replay tool would close, not a reason to switch testing platforms again.
The choice between a broader multivariate testing capability and a simpler A/B-only tool is one of the more common upgrade decisions a growing stack faces — and it's worth making deliberately, once traffic and page complexity actually justify it, rather than defaulting to the more complex tool because it sounds more advanced.
Questions people also ask
Do I need a separate heatmap tool if my testing platform already has one?
Only if the built-in version is genuinely thin. Some testing platforms bundle basic heatmaps well enough to skip a second tool; others bolt one on as an afterthought. Check a live example before assuming either way.
What's the minimum CRO stack for a small team?
One testing tool and one session replay tool. Add a survey or feedback tool once you have specific questions you can't answer from behavior data alone, and add a dedicated analytics platform only once your existing one genuinely can't answer a funnel question.
Is it worth paying for an all-in-one CRO platform instead of separate tools?
It depends on how much you value one login over best-in-class components. An all-in-one platform is usually weaker in each individual category than a specialist tool, but it saves integration time and keeps data in one place — a real trade, not a clear win either direction.
How often should a CRO stack be reviewed?
Roughly once a year, or whenever a tool stops getting used by the team. A subscription nobody opens anymore is a cost with no offsetting benefit, and it's worth cutting before it's worth debating whether to upgrade it.
Sources
- GrowthBook Documentation — GrowthBook (checked 22 September 2026)
- Statsig Documentation — Statsig (checked 22 September 2026)
- Conversion Rate Optimization Tools — Hotjar (checked 22 September 2026)
- Best A/B Testing Tools — Crazy Egg (checked 22 September 2026)
- Best A/B Testing Tools for Product Teams — Amplitude (checked 22 September 2026)
Get an honest read on what your CRO stack is missing
Book a free 30-minute consultation with Ibrahem and Jeremy. We look at your site while we talk, and you leave with a prioritised plan.
Who wrote this
Ibrahem HelalCo-founder
Leads strategy and delivery.
Works on: SEO, GEO
Reviewed before publishing by Jeremy Zava, Co-founder.
- A/B Testing: The Complete GuideWhat A/B testing is, when your traffic can support it, how to run a split test that holds up, and how to read the result without fooling yourself.
- Best A/B Testing Tools, ComparedA working list of A/B testing tools by team size and budget, with what each one actually changes about how you test and what it costs to run.
- 37 A/B Test Ideas Worth Actually RunningA practical list of A/B test ideas across headlines, pricing, forms and trust signals, grouped by where they tend to pay off and how to prioritize them.
- A/B vs Multivariate Testing: The DifferenceA/B testing compares whole page versions; multivariate testing isolates which element drives the result — and needs far more traffic to prove it.