Skip to main content

User Flows

See how users actually move through your app — which screens they visit, in what order, and where they drop off — across web and mobile. User Flows turns the screen views your SDK already sends into a visual journey map under RUM → User Flows.

Overview​

User Flows answers questions like:

  • Where do users start, and how do they branch out from there?
  • Which paths are common — and are people navigating differently than you expect?
  • Which screen is the biggest drop-off point (where sessions end)?
  • For a given screen, where do the drop-offs come from — which channel (web / iOS / Android), browser, or OS?
  • What did users do just before they left?

Everything is built from RUM screen view events, so there's no extra instrumentation beyond tracking screens.

How it works​

  1. Your app reports a screen view every time the user navigates (automatically — see the SDK guides below).
  2. Simplr reconstructs each session's ordered sequence of screens.
  3. The dashboard computes screen-to-screen transitions and drop-off, and draws a branching flow:
    • Nodes are screens. Colour shows drop-off rate (green → amber → red). An entry icon marks screens where sessions begin.
    • Edges are transitions, weighted by how many users went from screen A → B.
    • Click a screen to see its performance (views, sessions, avg time, drop-off %, error rate), where users go next / came from, and a breakdown of where it's used and where drop-offs come from by channel, browser, and OS.

Channels​

Each event is tagged with a channel (platform) automatically by the SDK:

  • web — the JavaScript SDK
  • ios / android — the Flutter (or native) mobile SDK

Use the channel selector on the User Flows page to view all traffic or focus on a single platform. This makes it easy to compare, for example, the checkout flow on iOS vs. web.

Get screen data flowing​

Screen tracking is built into the SDKs and needs almost no code:

Once the SDK is connected and tracking screens, journeys appear under RUM → User Flows within minutes.

Tips for clean flows​

  • Name your screens consistently (e.g. Checkout, Product Detail) rather than raw URLs/paths — flows group by screen name.
  • Keep names stable across platforms so web and mobile screens line up where they represent the same step.
  • Use the time-period selector to compare recent behaviour against a longer baseline.