Menu

CRO

Abandonment Analysis

A practical UX and analytics method for identifying where users leave key journeys before completing the intended goal.

How to use abandonment analysis to pinpoint drop-off points, uncover friction, and improve completion rates.

4 min read

What it is

Abandonment analysis is a UX and analytics method used to identify where users leave a journey before completing a goal.

It focuses on points within flows such as sign-up, checkout, or application .

By analysing , it reveals where users stop, hesitate, or fail to continue.

This can include reviewing , , and interaction patterns.

The focus is on identifying and understanding why users do not complete key actions.

The goal is to reduce and improve completion rates.

Abandonment analysis is most useful when teams need clear evidence of where journeys are failing before deciding what to fix.

When to use it

Use this method when users are not completing journeys.

It is most useful when:

you have clear conversion or completion goals
users are dropping off at specific stages
you want to improve funnels or flows
you need to prioritise fixes
you have behavioural data available

It is less useful when:

tracking data is incomplete
journeys are too simple or short
traffic is too low for meaningful analysis
Abandonment analysis is often used in CRO and UX optimisation.

Key takeaway

Use abandonment analysis when you need to prioritise fixes based on where users actually stop, not where teams assume problems are.

How to run it

Set up properly

Be clear on the journey, its steps, and what completion means. Abandonment is only measurable against a defined , so a browsing is not an abandonment.

Distinguish abandonment from deferral. Somebody returning three days later to complete has not abandoned anything, and single- measurement will record them as lost.

Run the method

Abandonment analysis focuses on leaving rather than progressing. It overlaps with and differs in : you are investigating a specific loss rather than measuring flow.

  1. Map the journey or as people actually experience it, including the steps you did not design.
  2. Identify the points between steps, in absolute numbers as well as rates.
  3. Analyse where people go when they leave: back a step, to help, to a competitor's tab, or away entirely. Each implies a different cause.
  4. Review supporting : , error logs, form analytics and support contacts for the same period.
  5. Compare segments, since abandonment is frequently concentrated in one device or one source.

Focus on cause rather than rate. The abandonment figure is a symptom, and improving it without understanding it usually means moving the problem earlier.

Capture and make sense of it

The value comes from understanding the loss. After analysis, document:

  • The points with the largest absolute impact
  • Likely causes, supported by evidence rather than
  • Findings validated with a second method before anybody redesigns
  • Improvements defined specifically enough to test

Use this to define improvements you can measure. Abandonment work is where quantitative and qualitative methods are most obviously complementary.

What to look for

Focus on:

Drop-off points: where users leave the journey
Patterns: consistent abandonment behaviour
Segments: differences between user groups
Friction: issues causing users to stop
Impact: which drop-offs matter most

Where it goes wrong

Most issues come from:

If you don’t understand why, you can’t fix it.

Counting deferral as abandonment, when people return days later to finish
Measuring the rate without investigating the cause
Looking only at the drop-off step, when the cause is often two steps earlier
Reading numbers without replays, errors or support contacts alongside
Improving the metric by moving the loss somewhere less visible

What you get from it

Done properly, this method gives you:

The drop-off points with the largest absolute impact
Causes supported by evidence rather than inferred from position
Where people go when they leave, which implies different fixes
Improvements defined specifically enough to test

Key takeaway

It helps you fix what’s stopping users.

Get in touch

If this sounds like something you need, we can help you analyse where users are dropping off and fix the issues that are costing you conversions.

No guesswork. No assumptions. Just clear insight into what’s going wrong.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is abandonment analysis in UX?

It is a method for identifying where users leave a journey before completing it.

When should you use abandonment analysis?

Use it when users are dropping off in key flows.

What can you analyse?

Funnels, forms, checkout flows, and multi-step journeys.

How do you find the cause?

Combine analytics with qualitative methods.

Does abandonment analysis improve UX?

Yes. It helps remove friction and improve completion rates.

Quick take

If users are dropping off, don’t guess why. Analyse where and when they abandon.

Related Services

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer