When a long conversion path is honest
Some apps earn a long path: regulated permissions, a two-sided marketplace, a saved item that must exist before a plan makes sense. Length is not automatically waste.
Field notes
Field notes
Short pieces from path reviews and clinics. They are about specific stalls in conversion sequences, not general essays on productivity.
Drop-off is not a verdict on a single screen
A stall on a permission prompt or paywall often starts on the previous screen. Conversion path analytics has to read the handoff, not isolate a villain.
What a first-session path looks like when we sit with it
A walkthrough of a first-session conversion path: welcome, permission, empty state, and the first saved item, as read in a Manchester briefing.
Event names that cannot reconstruct a conversion path
How a single event for both restore and fresh open quietly ruins conversion path analytics, and what a one-path dictionary should split.
The paid screen is a poor place to start a path review
Why conversion path analytics should begin two or three screens before the paywall, especially when a restore or a permission prompt sits in between.