2026-05-27 · 7 min read

Reading drop-offs without blaming the screen

A drop-off is a clue, not a diagnosis. Context before and after the event often changes the story.

A drop-off marks the last observed point in a defined sequence. It does not tell you why someone stopped, whether they intended to continue, or whether the measurement followed them correctly.

Check the trail first

Confirm that the next event fires reliably across platforms and versions. Look for identity changes, time-window assumptions, deep links and alternative success events. A tracking gap can resemble a product problem with surprising precision.

Look before and after the screen

Entry source shapes expectations. Prior errors shape patience. What appears to be a weak payment screen may start with unclear pricing much earlier. Likewise, some users return through another route or device and complete outside the funnel window.

Treat the screen as a location, not automatically a cause.

Compare sequences, segments and qualitative evidence before assigning responsibility.

Turn a clue into a test

Write competing explanations and identify what evidence would distinguish them. That might mean a cohort comparison, usability sessions, a tracking fix or a focused experiment. The objective is not to defend the funnel; it is to reduce uncertainty around the decision.

Apply this to your app

Move from a general pattern to your actual path.

Discuss a journey