How do you track customer journeys in SaaS?
Tracking customer journeys in SaaS means measuring a bounded path: a start event, a success event, and a stuck state when progress stops past a time threshold. You see who is stuck now, not only funnel totals. Nudge the users who stopped on the step.
You are not tracking every click. You are tracking one path where drop-off hurts retention. Example: start at /setup, success at /dashboard with a core action, stuck if no success in 48 hours.
| Completion rate | Status | Action |
|---|---|---|
| 70%+ | Healthy | Optimize copy and timing; watch for new bottlenecks |
| 50-70% | At risk | Find the step where users stop; fix or nudge |
| Below 50% | Critical | Redesign the path and nudge stuck accounts now |
A 65% completion rate is a portfolio number. Saves happen when someone acts on the stuck list this week.
For the signup-to-value clock, see time to value. For what to run when stuck fires, see the churn intervention playbook.
Frequently asked questions
How is journey tracking different from time to value?
Time to value is the clock from signup to first outcome. Journey tracking is the live state of a defined path, for example setup to dashboard. TTV is the outcome; journeys show where people stop along the way.
What should I do when an account is stuck in a journey?
Write to the users on that account who stopped. Name the missed step, or schedule a short call. Stuck journey is a catch signal; the save is a targeted unblock, not a generic check-in.
What completion rate should I treat as healthy?
Above 70% is healthy. Between 50% and 70% means find the step where users stop. Below 50% means redesign the path and nudge stuck accounts now.