Conversion Path Audit
A two-to-three-week reconstruction of the live sequence from first open to the paid or signup step, written so a product pair can change specific screens.
Conversion path analytics · Manchester
We reconstruct conversion paths from recordings, event names, and the screens themselves. Then we sit with the people who can change a prompt, a restore state, or a paywall copy block — not a slide that restates a funnel chart.
Service Routepoint is a conversion path analytics studio in Manchester. The work starts with a named sequence: which screen follows first open, which prompt interrupts it, and which event actually marks the paid or signup step. We do not treat a funnel export as the path. A funnel can hide a restore, a skipped permission, or a back-stack that returns people to an empty cart.
A typical briefing lasts forty-five minutes. You bring the current screen list, any session recordings you already collect, and the event names your engineers trust. We leave with a written path, the two or three stalls worth a closer look, and a proposed Conversion Path Audit if the sequence is messy enough to need one.
The studio does not sell a monitoring product, a dashboard licence, or a weekly automated digest. You book people who will read the path with you and write it down in language your design and engineering pairs can argue with.
A two-to-three-week reconstruction of the live sequence from first open to the paid or signup step, written so a product pair can change specific screens.
A half-day working session on one stubborn stall — a permission prompt, a restore, a paywall — with the people who can change that screen in the room.
A practical mapping of event names onto the live conversion path, so a later audit is reading the same sequence the app actually shows.
A Leeds-based subscription app asked us to sit with the sequence from push-driven re-open through to a yearly plan. The paid screen was tidy. The break was three screens earlier: a restored cart that quietly reset the trial clock. We wrote that finding as a path review, then walked the product pair through the recording timestamps they already owned.
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.
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.
A walkthrough of a first-session conversion path: welcome, permission, empty state, and the first saved item, as read in a Manchester briefing.