Mixpanel Flows: Finding Out What Users Actually Do (Not What You Designed)

Every product has two user journeys: the one in the design file, and the one users actually take.

The design file says: sign up, complete onboarding, create your first project, invite a teammate. The real journey, when you finally look at it, often goes: sign up, open settings, open billing, go back to the dashboard, open the help center, leave. Nobody designed that path. But a lot of users take it, and it tells you something important about what they’re worried about.

Funnels measure the path you designed. Flows show you the paths people actually take.

This guide covers how Mixpanel’s Flows report works, how to set it up so it’s readable, and the questions it answers better than any other report.

What Flows does

Mixpanel describes Flows as a report that identifies the most frequent paths users take to or from any event. You use it to understand how users move through your product step by step and to analyze drop-offs or unsuccessful behavior. Flows is available on all Mixpanel plans, free included.

Typical questions:

  • What do users do right after signing up?
  • What did users do just before they upgraded?
  • How do users get from the landing page to signup?
  • What do people do instead of completing checkout?
  • How do users move between account creation and their first key action?

How to build a Flows report

Step 1: Choose your anchor events

Anchor events are the fixed points of your analysis. You can pick one (“what happens after Sign Up?”) or several in sequence (“what happens between Landing Page and Sign Up?”).

With multiple anchors, Flows shows the paths between them. Mixpanel’s own example is the top paths leading Chrome users from a landing page to signup.

Step 2: Choose steps before and after

For each anchor, choose how many steps to show before and after. By default, Mixpanel shows the first three events after the selected event. You can add more directly in the chart: the plus on the right adds later steps, the plus on the left adds earlier steps.

With multiple anchors, there’s a breakpoint between them. Adding steps on either side of the breakpoint shows what happened right after the first anchor or right before the second.

Step 3: Pick a counting method

Like Funnels, Flows can count by uniques, totals or sessions (post 9 explains the difference). Sessions are particularly useful in Flows, because they keep the path inside one visit.

Step 4: Filter and break down

Add filters to focus on a segment, such as one platform or one acquisition channel. Breakdowns let you compare how the whole journey differs between groups. Mixpanel’s docs describe the breakdown feature as a way to see how complete user journeys differ across audience segments.

Reading the two visualizations

Flows has two main views.

User Flows (Sankey)

The default is a Sankey diagram showing multiple paths at once. The width of each bar and connecting line represents how many users took that route. At each step, Mixpanel shows the top three events by number of users; less common ones are grouped into Other events, which you can expand. You can also change how many rows to show at once in the advanced settings.

The Sankey is best for spotting big branches: “40% of users go to settings right after signup.”

Top Paths

Top Paths condenses the flows into unique complete sequences, ranked by frequency. Community answers from Mixpanel note it shows the most common sequences, up to the number of steps you selected.

Top Paths is best for spotting specific routes: “the third most common path after signup is pricing → billing → logout.”

I use both. The Sankey shows the shape; Top Paths gives you the exact sentences to put in a report.

Making Flows readable: hide the noise

The single biggest reason teams give up on Flows is noise. If you track page_viewed, scroll_depth, heartbeat and api_call_succeeded, every path is cluttered with events that don’t describe decisions.

Mixpanel lets you hide events from a flow, either with the Hide Events button or by right-clicking an event in the chart. I hide anything that isn’t a meaningful user action before I start analyzing.

Two other tricks:

  • Use custom events (post 16) to group related actions. Three different share buttons become one Content Shared step, which makes paths much simpler.
  • Break page_viewed out by page name only when the page matters. For product flows, it’s often better to hide generic page views and look at actions.

Workflows I use with clients

Investigating funnel drop-off

Funnels tell you where people leave. Flows tells you where they go instead.

  1. In your funnel, find the step with the biggest drop.
  2. Open Flows with the step before the drop as the anchor.
  3. Look at the next two or three steps for users who didn’t continue.
  4. Look for a common detour: help docs, pricing, settings, a back button.

Mixpanel lets you view a funnel’s drop-off as a flow directly, which makes this quick.

Understanding what precedes conversion

Anchor on your conversion event (upgrade, purchase, invite) and add steps before it. The most common preceding actions are strong candidates for your activation metric, and for things to put in front of new users sooner.

Onboarding reality check

Anchor on signup, show five steps after, break down by platform. Compare the paths to the onboarding you designed. Where they differ, you’ve found either a UX problem or a better path than the one you designed.

Comparing segments

Break down by new vs returning users, or by acquisition channel. Paid social users often behave very differently in their first session from organic search users, and Flows shows that at a glance.

When Flows is the wrong tool

  • For measuring conversion rates over time, use Funnels. Flows is exploratory.
  • For long-term behavior, use Retention. Flows looks at sequences of events, not weeks of engagement.
  • When your tracking is too thin. If you only track five events, Flows has very little to show.
  • When your tracking is too noisy and you haven’t hidden the noise.

Mistakes to avoid

  • Not hiding background events. The paths become unreadable.
  • Too many steps at once. Start with three, then expand.
  • Ignoring Other events. Sometimes the interesting path is the one that didn’t make the top three.
  • Drawing conclusions from tiny segments. A path taken by 12 users is a hint, not a finding.
  • Using Flows to report numbers to leadership. Use it to find the story, then measure it with a funnel or Insights.

Final thoughts

Flows is the report that most often surprises my clients, because it shows behavior nobody planned for. Use it to explore, hide the noise ruthlessly, and turn every surprising path into a question you can measure properly.

Sources