Customer Analytics
Intermediate 14 min read Customer Analytics

Customer Journey Analysis

Every customer takes more than one road

Customer journey analysis maps the paths users take from first touch to churn, exposing the mix of routes, the junctures where users diverge, and the moments that most strongly predict conversion.

customer journeypath analysistouchpointsjourney mappingconversion paths
Before we start

What you will learn

  • Build journey maps from ordered event sequences
  • Find the paths that correlate with conversion and churn
  • Identify friction junctures and design fixes
Introduction

What is this?

Customer journey analysis is the study of sequences — ordered strings of touchpoints (ads, emails, onboarding steps, purchases). Instead of a single funnel, it treats every customer's path as a story, then aggregates those stories into the most common and most valuable routes.

Motivation

Why do you need it?

  • Most products have many entry points; a one-funnel view misallocates fixes.
  • High-converting paths reveal migration opportunities for the rest.
  • Journeys expose cross-channel behavior that cohort and funnel views miss.
Think about it

Mental model

Imagine

Clickstream breadcrumbs of every visitor

Think of

A city's traffic network

You do not analyze one road; you analyze the network to find where congestion forms and which routes lead to the shops.

Mechanics

How it works

  • Collect ordered event sequences per user with timestamps.
  • Aggregate path transitions into a transition matrix or tree.
  • Attach outcomes (conversion, churn, spend) to each path prefix.
  • Surface the highest-volume and highest-value routes for discussion.

Journeys diversify from acquisition into many paths that re-converge at value.

Acquire
Onboard
Diverge
Outcome
Real world

In production

  • Onboarding is redesigned around the highest-converting journey paths.
  • Marketing weights channels by the downstream probability those users convert.
  • Churn analysis adds the usage path before leaving as a new signal.
Guidelines

Best practices

  • Track journeys at the identity level and keep timestamps consistent.
  • Compare observed paths against a small set of design-intended paths and focus on volume-weighted payoff.
Watch out

Common mistakes

  • Mixing top-of-funnel traffic and returning-user journeys in the same graph.
  • Optimizing for path diversity when the product is actually single-funnel.
When things break

Debugging tips

  • If one path dominates, verify the funnel instrumentation is not echoing default navigation.
  • If journeys look random, check that session boundaries are being split correctly.
Interviews

Interview checkpoint

Test yourself

Quick quiz

0/2
1

Journey analysis is based on

2

A high-converting but low-volume journey should be weighted by its size when prioritizing fixes.

Go deeper

Official documentation