Insyt
All charts in the library

Flow, process and networks

Fallout diagram (continuation and drop-off)

Shows users continuing through or leaving a predefined sequence.

  • Diagram
  • Conversion
  • Drop-off

What it answers

At which prescribed steps do users leave?

Shape
Sequential stages and exit branches
What it shows
Continuation and stage-specific loss.

Example

The question

At which step of sign-up do people give up?

Sign-up steps with drop-off at each step, September

Sign-up steps with drop-off at each step, SeptemberOne bar per step; the pink end of each bar is the people who leave before the next step. Start 1000; Email 720; Details 540; Verify 410; Done 380. The biggest drop is at the start (280 leave before giving an email).Start1000−280 leftEmail720−180 leftDetails540−130 leftVerify410−30 leftDone380
Sign-up steps with drop-off at each step, SeptemberOne bar per step; the pink end of each bar is the people who leave before the next step. Start 1000; Email 720; Details 540; Verify 410; Done 380. The biggest drop is at the start (280 leave before giving an email).Start 1000−280 leftEmail 720−180 leftDetails 540−130 leftVerify 410−30 leftDone 380
One bar per step; the pink end of each bar is the people who leave before the next step. Start 1000; Email 720; Details 540; Verify 410; Done 380. The biggest drop is at the start (280 leave before giving an email).

Illustrative data. It belongs to no company.

When to use it

Use it when

Testing a specific expected journey.

Avoid it when

When the task is open-ended path discovery.

How to read it

Follow ordered steps and exit branches using the cohort rules.

Note

Define ordered-event rules, user/session scope and time window.

The data you need

Layout
Ordered event log
Fields
EntityID or SessionID: text; Event: text; Timestamp: datetime
One row is
One recorded action by one user or session. What is the grain?
Rules
Sort within entity/session. Define event order, identity, sessionisation, repeated-event and window rules.
Optional
Stage definitions for fallout; EventID for ties; preaggregated Source,Target,Count if full paths are unnecessary.
Preparation
Resolve user/session/case identities; sort within each trace and define ties, repeated events, windows and start/completion semantics before deriving links.
Units
Counts may mean users, sessions, cases or events; state which. Conversion uses eligible entities, and durations require explicit time units.
Example of the input layout: Ordered event logAn event log: one row per event, with a case ID, activity and timestamp.CaseActivityTime1Start09:001Check09:201Done10:052Start09:102Check09:40
An event log: one row per event, with a case ID, activity and timestamp.

Worked example

Of 100 visits,20 reach trial and 5 purchase in the window. Drop-off is 80 before trial and 15 between trial andpurchase.

EntityIDEventTimestamp
U1Visit2026-01-01T10:00:00
U1Trial2026-01-01T10:05:00
U2Visit2026-01-01T11:00:00
All charts in the library