Customer journey mapping

What customer journey mapping is.

A customer journey map is a picture of the steps someone goes through from first noticing a need to buying, and often beyond that to renewing or recommending. For each step, it records what the person is trying to do, where they're doing it, what they're unsure about and what makes them stop.

Most maps use stages such as awareness, consideration, purchase and retention. The stage names matter far less than what sits under them. A useful map tells you which question a buyer has at each stage, whether your site or your ads answer it, and how many people you lose at that point.

There are two common kinds of map. A current state map shows what happens today, and a future state map shows what you want to happen. We start with the current state, because you can't plan a fix for a problem you haven't located.

When a customer journey map makes sense.

Mapping is useful when something is clearly leaking and nobody agrees where. Traffic looks healthy and sales don't follow, or each team has its own explanation for why leads go cold. It also helps before a new campaign or website, when you're about to spend money on assumptions about how people buy, and when a long sales cycle with several decision makers can't be seen in any single report.

We'd skip it if you sell one simple product through one channel and already know where people drop off. A conversion audit would probably get you there sooner.

Where the evidence comes from.

Workshops are good at collecting what your team believes about customers. We treat those beliefs as things to check against two other kinds of evidence.

Behavior data shows what people did. Analytics, ad platforms, Search Console and your CRM can show which searches bring people in, which pages they land on, where they drop off and how long leads take to close. This data has gaps, because consent choices, ad blockers and switching devices all break the trail. No tool can show you the complete path of every person, so we mark where the data stops.

Conversations show why people did it. Interviews, sales calls, support tickets and reviews tell you what buyers compared you against, what worried them and which words they used.

The part your analytics can't see.

The comparison stage is often the thinnest part of a map, because so much of it happens away from your site. People read reviews, ask colleagues, watch videos, check forums and put questions to AI assistants. By the time they land on your pricing page, they may have already decided who's on their shortlist.

We look at this stage from the outside. We run the searches a buyer would run, read what comes up and note what people find about you and the alternatives. We also ask customers directly how they made the decision, since that's often the only record of it.

Finding where you lose people.

Once the stages are clear, we estimate how many people get through each one and label which figures are measured and which are estimates. We then look at what each loss is worth. A big drop early on, among people who were only browsing, can be normal. A small drop just before purchase can cost you far more.

We also check that a drop-off is real. A step that seems to lose everyone can turn out to be a step where the tracking stopped working, and that has a very different fix.

How we measure customer journey work.

A map has done its job when it changes a decision, so the first thing we look at is whether the fixes get made. For each fix, we name the number it should move before the change goes in, such as the share of visitors who reach the form or the share of leads who book a call.

We then compare that number before and after, and we say plainly when something else could explain the change, such as a season or a shift in traffic.