User Flow

User flow is the sequence of pages and events a visitor moves through during a single session — from entry, through middle steps, to either a conversion or an exit. In Google Analytics 4, the original Universal Analytics “User Flow” report no longer exists. Its replacement is Path Exploration, found inside Explorations. This guide covers what user flow really means, how Path Exploration works in GA4, the differences between user flow, customer journey, and funnel analysis, plus the audit patterns that turn flow data into action.

What Is a User Flow?

A user flow is the actual sequence of screens, pages, and GA4 events a visitor triggers between landing on a site and leaving it. Each node represents a page view or event. Each edge represents a transition. The flow can branch — most users do not follow one straight line. They loop, backtrack, and exit at different points.

User flow analysis answers different questions than a single metric does: “where do people actually go after the homepage?”, “which step loses the most users before checkout?”, “which entry pages send visitors deeper into the site, and which dead-end them?”. A flow turns isolated pageview counts into a connected map of behavior.

User Flow vs User Journey vs Customer Journey

These three terms get used interchangeably in marketing decks, but they describe different scopes:

User flow is the narrowest. It is the on-site, in-session behavior you can see in your analytics tool. The customer journey is broader — it includes ads they saw on Instagram, the email they opened, the support chat they started, and the call they took with sales. Treat them as zoom levels of the same underlying truth.

The Universal Analytics User Flow Report (Legacy)

Universal Analytics, sunset on July 1, 2023, had a built-in Behavior Flow and a separate Users Flow report. Both lived under Behavior > Behavior Flow. They visualized traffic moving from landing pages through subsequent pages as a Sankey-style diagram, with red drop-off bands at each step.

That report was easy to read but had real flaws: it sampled data heavily, hid loops, and limited node depth. Users had to scroll horizontally to follow long paths. It also could not include events as nodes — only pageviews. When GA4 launched, Google dropped the report entirely and shipped a more flexible replacement instead.

GA4’s Replacement: Path Exploration in Explorations

Path Exploration is GA4’s user flow successor. You’ll find it inside Explore > Path Exploration. It builds an interactive branching tree of nodes, where each node can be a page, screen, or event — not just a pageview. Users can click any node to expand the next step or trace the previous one.

Three things make Path Exploration more useful than the legacy report:

• Events as nodes. You can chain pageviews and custom events in one tree. A view_item followed by add_to_cart followed by begin_checkout is now a single readable flow.
• Reverse path analysis. Pick an end point (an exit page, a conversion event) and trace backward to see how users got there. This is how you debug high-exit pages.
• Live segmentation. Apply any segment — by source, device, geography, or audience — and the tree rebuilds in seconds.

How to Build a Path Exploration in GA4 (step-by-step)

The setup takes about two minutes. Open GA4 and do the following:

1. Open Explore. In the left nav, click Explore. Pick Path Exploration from the template gallery.
2. Choose direction. Top right of the canvas: pick Start over to clear the default tree. Then click either “Starting point” (forward path) or “Ending point” (reverse path) in the top bar.
3. Set the anchor node. For a forward path from the homepage, click Starting point, choose Page title and screen name, and pick your homepage. For a reverse path from a checkout failure, click Ending point and pick your checkout_error event or the cart URL.
4. Expand the tree. Click any subsequent node to drill deeper. Each click opens the next step’s most-frequent transitions.
5. Switch dimension. Above each step you can toggle between Page title, Page path, and Event name. Mix them mid-flow to see “page → page → event” sequences.
6. Apply a segment. Drag any segment — Mobile traffic, Paid search, Returning users — into the Segment comparisons field on the left to compare flows side by side.
7. Export or share. Top-right of the canvas, click the share icon to send the exploration link to your team. The state is saved per user.

Path Exploration uses the standard GA4 reporting tables, so it is not sampled the way UA Behavior Flow was. For the technical details, see Google’s official Path Exploration documentation.

Forward vs Reverse Path Exploration — When to Use Each

The same tool, two opposite questions:

• Forward path: “If a user lands on X, where do they go next?”. Use it to optimize entry pages — homepage, blog hub, paid landing. You’re asking: which next step is the most popular, and is it the one I want?
• Reverse path: “Before users reached X, what did they see?”. Use it to debug exit pages, abandoned carts, or unexpected conversion sources. You’re asking: where did the funnel break, or which surprise referrer is sending qualified visitors?

A common workflow combines both. Run a reverse path from your top exit page to find the upstream pages causing drop-off. Then run a forward path from those upstream pages to confirm the leak. The two views together give you a closed-loop diagnosis instead of an isolated metric.

Common User Flow Patterns to Audit

Most flow problems fall into a handful of recognizable patterns. When you open Path Exploration, scan for these first:

• Dead-end entry pages. Visitors land, view one page, exit. The page satisfies the search query but offers no next step. Fix: add a clear CTA, related-content links, or an inline conversion path.
• Loop traps. Users bounce between two pages — usually search results and an unhelpful detail page. The loop signals a content gap or weak filtering. Fix: improve the detail page, add facets, or rework site search.
• Drop-off at form pages. Heavy traffic enters a form page, almost no one submits. Causes are usually slow load, too many fields, or an unclear value proposition. Fix: simplify, prefill, and verify the form fires its GA4 events correctly.
• Unexpected exits high in the funnel. Users abandon before reviewing the product or pricing. Often a page-speed issue or a confusing first-fold layout.
• High-engagement orphan pages. Pages with strong engaged sessions but no internal links pointing to them. Visitors read, then have nowhere to go. Fix: add contextual cross-links from related pages.

For a deeper dive into the exit-side of this analysis, our pillar guide on exit pages analysis walks through a full reverse-path workflow with real screenshots.

User Flow vs Funnel Analysis — When to Use Which

Path Exploration and Funnel Exploration are siblings in the GA4 Explorations menu, but they answer different questions:

Use Path Exploration when you don’t know the path users actually take, when you’re auditing a redesign, or when you’re diagnosing high exits. Use Funnel Exploration when you already know the steps users should take and you want to measure how many make it through each one. For an end-to-end example tying flows to revenue, see our pillar guide on checkout funnel analysis.

GA4 Path Exploration vs UA Behavior Flow — feature parity

Frequently Asked Questions

Related Terms

• Session — the time window inside which a user flow is measured
• GA4 events — the building blocks that become nodes in Path Exploration
• Conversion — the desired endpoint of any user flow
• Engaged sessions — quality filter for flow analysis
• Pageview — the original node type in legacy flow reports