Skip to content
CRO expertise

CRO and behavioural analysis

User journey analysis, hypotheses or gut feeling, A/B testing, reading the results and optimising: my expertise comes from 10 years turning behavioural data into improvements for large organisations.

10 years
of behavioural analysis and testing
4
large accounts supported: insurance, telecom, banking, retail
6
analysis and testing tools mastered

2 ways to work together

On contract within your team
3 to 12 months, testing programme, journey analyses, monitoring dashboards. Freelance profile
As a fixed-price project
Journey audit, one testing cycle, setup of an A/B testing or behavioural analysis tool.
With your teams
I help the teams read the results and prioritise the next hypotheses.

From observation to decision

CRO starts with an in-depth analysis of the user journey. The A/B test comes in as support, when a doubt remains or several solutions look equally good on paper.

How I spot a friction point

Session recordings, heatmaps and funnels in Contentsquare or Hotjar, crossed with the events, conversions and segments of GA4, Piano or Adobe Analytics: these sources give the visitors' complete path, from the source and landing page to the point of conversion, dispersion or drop-off. Often, the root of the problem is not where we thought.

  • Tracing the real journey: previous page views, interactions, reaction time
  • Mapping friction and drop-off points, by segment and by device
  • Hypothesis written with the product and marketing teams, backed by data

The A/B test, a validation option

When the analysis clearly points to the problem and its solution, it is enough. The A/B test comes into play when a doubt remains about the right approach, or to decide between several plausible solutions before rolling out a change.

  • Launched to settle a doubt
  • Subject to the traffic and time required
  • Quantified result before going to production

A complete CRO programme

A method to turn observation into decision, A/B tested where needed.

  1. Journey audit

    Qualitative analysis (session recordings, heatmaps) and quantitative analysis (GA4, Piano or Adobe Analytics data) crossed to spot the friction points.

  2. Hypothesis

    Each friction becomes a clear hypothesis about its cause and its fix, ranked by estimated impact and implementation effort.

  3. Test when in doubt

    Variant built in an A/B testing tool, audience and duration framed, monitored in parallel in the web analytics solution.

  4. Reading the result

    Statistical significance checked, result read by segment before any rollout to all traffic.

  5. Decision, adaptation

    Summary, implementation or abandonment of the variant, backlog updated for the next friction.

CRO situations solved

A problem, an analysis and solutions tested where needed.

Insurance, hospitalisation page

A comprehension problem that diverted traffic

Only 20% of the page's visitors clicked the target button "My Healthcare". Tracing their journey in GA4, a large share of the remaining 80% (40% of the total) headed instead for "Log in" in the header. These visitors had hospitalisation cover through their employer but did not know it was called "My Healthcare". So they looked for it in their account, where it did not appear.
An A/B test displayed a popup on clicking "Log in", offering 2 clear paths, "My account" or "My hospitalisation insurance", to validate the intent. 2 visitors out of 3 chose "My Healthcare", confirming the hypothesis. The popup was removed and the page reworded accordingly, fixing the traffic flow.

E-commerce, claims service

Same need, 2 very different CTRs

The CTA to the claim form had an average CTR of 26%, decent for this type of page. But splitting by the 2 pages that led to it, the gap appeared: 34% from "All digital services", only 20% from "All services". On the latter, the "Track a claim" link was placed before the "File a claim" link: a visitor looking to file a claim clicked that first link before even seeing the second.
The 2 links were swapped, "File a claim" first. The CTR from "All services" went from 20 to 28%, bringing the CTA's overall CTR from 26 to 32%.

The analysis and testing tools I work with

For the tracking foundation, see the tracking expertise. For reporting, the Data Studio dashboards.

The questions I get asked about CRO

It depends on the current conversion rate and the uplift you want to detect. With modest traffic a test is still possible but runs longer or targets a larger uplift. The calculation is done before launch.

No. The behavioural analysis and the first hypotheses are built with what you already have (web analytics solution, session recordings if available). The testing tool is chosen once the first programme is framed, if needed.

Not yet. 3 days cover neither a full weekly cycle nor a sufficient sample in most cases. We wait for statistical significance and a complete cycle before concluding.

No, it is the first condition. A test measured on incomplete tracking data produces false conclusions. If the tracking is not reliable yet, we start there: see the tracking expertise.

Yes, the behavioural analysis and testing method stays the same whatever the web analytics solution: what matters is how the programme is organised, not the tool.

Ready to take action?

Tell me about your site and your Ads platforms: you get a clear answer within 48 hours.

Get a quote