CRO Tools for UK Businesses: The Analytics, Testing and Recording Stack

A working CRO programme needs tools for four things: analytics that shows where visitors drop out, testing platforms that split traffic between variants, session recording and heatmaps that show why visitors behave the way they do and form analytics that shows which fields cause abandonment. This guide covers what each layer does and which tools UK businesses tend to use and sits inside the wider conversion rate optimisation for UK businesses discipline.

The Google Analytics developer documentation is the reference point most teams already know for the analytics layer.

The analytics layer

Analytics is the foundation. Without reliable analytics no downstream CRO work makes sense, since there is no baseline to measure improvements against. GA4 is the default choice for most UK businesses, since it is free, well supported and integrates with the wider Google marketing stack. Alternative platforms exist for teams that need first-party data control, but the cost usually only makes sense for larger accounts.

What matters more than the platform is the setup. Events tracking, goal configuration, cross-domain measurement and consent handling all need to be configured correctly before the numbers coming out are reliable. Sites running with default GA4 configuration are usually missing the events that CRO analysis depends on, particularly form interactions, scroll depth and outbound clicks.

The Search Engine Journal coverage of GA4 is a useful primer for teams new to the platform. Once analytics is set up properly, the questions it answers are: where do visitors drop out of the primary conversion funnel, which pages have the highest exit rates before conversion and which traffic sources produce the visitors most likely to convert.

Testing platforms

A/B testing platforms split visitor traffic between an original page and one or more variants, measure conversions on each and produce statistical read-outs on which variant performs best. The market has consolidated in recent years. The Search Engine Journal coverage of personalisation gives a wider view for enterprise buyers.

Buying a testing platform before there is a testing process to feed it is the most common way tooling investment on this layer goes wrong. The tool sits idle where the team tries to build the hypothesis pipeline that should have been built first.

Session recording and heatmaps

Session recording tools capture what individual visitors do on the page, so the team can watch back exactly where they hesitated, what they clicked, where they scrolled and where they gave up. Heatmap tools aggregate that behaviour across many visitors to show which areas of a page get the most attention.

Both layers answer the “why” question that analytics leaves open. Analytics can tell you that a large share of visitors leave a page without converting. Session recording tells you that a significant proportion of them scroll to the enquiry form, hover over a specific field then close the tab. That is where the hypothesis for the next test comes from.

The tools that dominate this layer for UK businesses are Hotjar, Microsoft Clarity and FullStory. Microsoft Clarity is free and has become the default starting point for smaller UK accounts. Hotjar offers deeper integrations for teams already using it as their heatmap tool. FullStory sits at the enterprise end with more sophisticated analytics on top of the raw session data.

Form analytics

Form analytics tools measure which fields cause the most abandonment, how long visitors spend on each field, which fields cause corrections and where visitors give up entirely. That data is the starting point for any form CRO work covered in the form CRO guide.

Form analytics tools deserve their own layer since standard analytics rarely captures field-level interaction. Sites that add a form analytics tool for the first time almost always find that the primary enquiry form is bleeding completions on a specific field the team had not identified as a friction point. The insight pays back the tool cost inside a month.

Zuko and Formisimo are the two form analytics tools most UK teams end up with. Both integrate with GA4 for cross-referenced reporting. The Baymard Institute checkout usability research is the reference library most form analytics recommendations trace back to.

The GDPR consideration

Most CRO tools now handle UK GDPR compliance with proper configuration, but the defaults are rarely compliant out of the packaging. Session recording tools that capture keystrokes, mouse movements or on-page interactions need consent under UK data protection rules. The ICO position on tracking has hardened in recent years, particularly around session replay.

• Personal data masking must be enabled on any session recording tool before it captures a single visitor.
• Cookie consent integration needs to gate the recording tool loading, not just the reporting dashboard.
• Data retention limits should be set to the shortest window the team can act on.
• The privacy policy needs to describe the tool by name and function, not by generic category.

Getting compliance wrong on the CRO tool stack exposes the organisation to a risk far larger than the marginal insight the tools provide. The compliance work needs to sit alongside the tool selection, not after it.

Building a working stack

The right order is process first, tools second. Buying a testing platform, a heatmap tool and a form analytics tool without a review process around the outputs produces dashboards nobody looks at. The tool spend continues, the CRO output does not.

A working stack for a mid-market UK B2B business usually starts with GA4 for analytics, Microsoft Clarity for session recording and heatmaps and a form analytics tool once the enquiry form is being actively optimised. A testing platform gets added when the traffic base supports it and the team is ready to run tests regularly.

Once the process is running, the tools amplify it. Before that, they sit idle. Where the CRO tool overlap with SEO tools becomes relevant, the CRO vs SEO overview covers the shared surface. The wider practice around what the tools support sits inside the CRO framework guide.