Skip to main content
User paths show the actual paths people take through your site and product, not only the paths you designed. Unlike a funnel, which follows a fixed sequence, user paths show every common transition, including unexpected ones. You can learn:
  • What do people do right after they sign up?
  • Where do new visitors go after the landing page?
  • Which pages lead to a signup, and which paths do not?
  • Where do people leave between two important steps?

Create a user paths chart

User paths is a chart type on a dashboard.
  1. Open Dashboards and open or create a dashboard.
  2. Click Add chart and choose the User paths metric.
  3. Set the steps and options below.
  4. Click Save chart.
The chart uses the dashboard date range and filters.

Settings

The role of a step depends on its position:
  • Start (the first step): the paths begin here. With only a start, the chart shows where sessions go next.
  • End (the last step, when there are two or more): only sessions that reach the end within the conversion window show. The path stops at the first end.
  • Anchors (the steps between): sessions must pass them in order.

Read the chart

The chart is a Sankey diagram. Each column is one step. Each node is a page path or a custom event, with its share of the sessions and its session count. Each ribbon is the sessions that went from one node to the next. Hold the pointer on a node or ribbon to see the counts.
  • Others groups the less frequent pages and events of a column. Its tooltip lists what it includes.
  • Drop-off (gray, only with two or more steps) counts the sessions that reached a step but did not reach the next step within the conversion window.
How the chart counts:
  • It counts sessions, not events or people. A session that does an event three times counts once. One user on two browsers counts as two sessions.
  • A session is the same session as on the Overview. It has at least one event that the website or the game sent (a page view, a custom event, or an event of a game or app build). An event without a session ID (for example a server event) is in the path of the session that it joins.
  • All steps must happen in the date range and within the conversion window of the first step. A path that continues after the last day of the range stops there.
  • When two events have the same time, the page view comes first.
  • Report filters apply to every event in a path.

Tips

  • Start with Any page view to see the common entry paths, then add an end step such as signup_completed to see only the paths that convert.
  • Exclude noisy events (for example, a heartbeat event) so the paths are easy to read.
  • Use user paths to find the steps for a new funnel. Then measure the conversion rate between them with a funnel. A funnel counts people; user paths count sessions, so the numbers can differ.
  • Give custom events clear, stable names, so the paths are easy to read.