Cohorts that lie about churn
A missing mid-path event invents drop-off that the product never caused.
Product meetings escalate when a cohort chart shows a steep cliff between day one and day seven. Sometimes that cliff is real. Often the second return event never fired after an OAuth redirect, or only fired on one OS.
Before rewriting onboarding, walk the path on devices your users hold and watch the live stream. Note every silent miss. Ask whether the step is client-only, server-confirmed, or both.
Identity resets between web and app are another quiet culprit. Users who continue on a second surface look like new entrants who churned. Cohort Path Diagnostic exists to catch that before the roadmap absorbs the wrong story.