Skip to main content

User journeys

User journeys help you understand the sequence of pages or product steps people follow. Instead of looking at every page in isolation, use a journey view to explore how one interaction leads to another and where users branch, loop back, or leave.

Questions journeys can answer

  • What do visitors commonly view after a landing page?
  • Which pages tend to appear before signup or purchase?
  • Do users take different paths to the same outcome?
  • Where do people go after encountering a help or pricing page?
  • Does a new navigation structure change the paths people take?
Journeys are descriptive: they show recorded sequences, not necessarily the motivation behind a user’s choice.

Investigate a journey

1

Choose an entry point or audience

Start with a page, screen, or segment tied to the question. Use a consistent date range and avoid comparing different audiences without accounting for their differences.
2

Read the next steps

Follow the most common transitions and notice less frequent branches that may be important. Keep in mind that common behavior is not always the behavior that creates the most value.
3

Find the point of friction

Look for loops, repeated visits to the same step, exits before a key action, or paths that differ between users who complete a goal and those who do not.
4

Compare against a goal or funnel

Use a goal to define the outcome and a funnel to quantify progress through the key steps. Journeys are useful for exploring paths; funnels are useful for measuring a defined sequence.
5

Inspect sessions for context

Review relevant session replays when you need to understand how a transition occurred or whether the interface may have caused confusion.

Tips for meaningful analysis

Keep the question narrow. A journey from the homepage to signup is easier to interpret than an unrestricted path across an entire product. Compare equivalent groups. When comparing campaigns, device types, or time periods, keep the date range and journey definition consistent. Distinguish correlation from cause. A page that appears frequently before conversion may be helpful, but the journey alone does not prove that the page caused the conversion. Check tracking coverage. Missing events or pages can make a path look incomplete. Verify collection before interpreting a missing transition as user behavior.

Journeys vs. funnels

Next steps

Use funnels to measure the flow you discovered, create a relevant goal, and review session replay for qualitative context.