Permission dialogs that invent funnel cliffs

A step that fires after a system prompt can look like mass abandonment.

Code on a laptop next to a coffee cup

On mobile, a conversion step that sits behind a notification or tracking permission can silently fail for half the cohort. The chart shows a cliff; the product never asked those users to leave.

Before rewriting the flow, walk the path on the devices your users hold and watch the live stream. Note client-only fires versus server confirmation. Check web-to-app identity continuity.

A Conversion Path Clinic stays narrow on purpose: one path, deep QA, a checklist you can rerun after every release so the cliff does not return unnoticed.

All journal entries Talk through a similar issue