Jump to section
Engagement is the leading indicator that tells you an onboarding is on track before any deadline confirms it. A customer who keeps showing up – opening the plan, finishing forms, logging into the product – almost always reaches value. One who goes quiet has usually stalled weeks before a milestone officially slips. The problem is that most teams only track outputs – tasks marked done – and find out about disengagement far too late, once the customer is already hard to win back.
Why engagement is the leading indicator
Tasks lag; engagement leads. A task marked "done" only confirms something already happened – it can't warn you about the customer who has quietly stopped showing up but hasn't missed a deadline yet.
That's why the default signals teams rely on fail them: they're all lagging. An unanswered email looks like a busy week. A postponed call looks like a calendar problem. Nothing in a spreadsheet tracker turns red when a customer loses momentum – the tracker just stops being updated. Making engagement observable is what lets you see the stall while it's still cheap to fix. (For the metrics that sit alongside engagement, see our guide to SaaS onboarding metrics and KPIs.)
The two levels of engagement to track (especially for SaaS)
For a software or tech company, "engagement" actually splits into two distinct things, and you need both:
- Process engagement – is the customer engaging with the onboarding itself? Are they opening the shared plan, completing intake forms, replying in the workspace, showing up to calls? This is the earliest signal, and it applies to every kind of onboarding, from SaaS to agencies to professional services.
- Product engagement – is the customer actually using your product? For SaaS and AI companies, this is where value is realised: first login, key actions taken, teammates invited, activation events fired. This level typically lives in a product analytics tool like Mixpanel, PostHog, or Amplitude.
The two diverge in revealing ways. A customer dutifully completing onboarding tasks but never logging into the product is on track on paper and churning in practice. A customer using the product heavily but ignoring the onboarding plan may not need as much hand-holding as their task list suggests. You only see the full picture when you watch both – process engagement for whether they're moving through onboarding, product engagement for whether they're getting value.
(For non-software teams – agencies, service businesses – the product-engagement layer often doesn't apply; process engagement is the signal that matters.)
What to track in onboarding
You don't need a data project to track process engagement. A handful of signals carry most of it:
- Workspace activity – who opened the onboarding material, when, and how often. A drop-off after kickoff is the classic early warning.
- Task and form completion – progress against the shared plan, and which items are sitting open or overdue.
- Who's engaging – whether the actual decision-makers are showing up, or a single stakeholder is carrying all the activity while the people who matter never appear.
- Response and meeting cadence – replies in the workspace and kept-vs-postponed check-ins. A customer who postpones the same call twice has given you your earliest churn signal.
On the product side, track your activation events – the specific actions that, in your data, separate accounts that retain from accounts that don't.
Space and block-level analytics
The hard part has always been making process engagement visible without manually chasing status. This is where a purpose-built onboarding platform earns its place. In Valuecase, each customer gets their own branded Space – the single login-free place they open to get onboarded – and engagement on that Space is tracked automatically: who opened it, what they viewed, and how activity trends over time.
That block-level detail is what turns guesswork into signal. Instead of "I think the Acme onboarding is going fine," you can see that their champion opened the plan three times this week but the technical stakeholder hasn't viewed the integration section at all – so you know exactly where the drop-off is and who to nudge. Across a portfolio, an engagement score per Space is the difference between managing forty onboardings and managing by anecdote: you see at a glance which customers are active and which have gone dark. Our guide on tracking onboarding completion without chasing covers how this rolls up into a self-tracking process.
Turn signals into action
Signals only help if someone acts on them, and "someone reads every dashboard every morning" doesn't survive a real workload. Two moves close that gap.
First, surface the signals in one view. A dashboard that shows every active onboarding with progress and last activity, plus saved views like "no customer activity in 7 days," turns the whole portfolio into a short, prioritised list.
Second, let automation act on the routine cases. Automated reminders nudge customers on overdue tasks and unfinished forms, which quietly resolves most slow-downs before anyone on your team lifts a finger. AI takes it further: onboarding risk scoring combines engagement, task progress, and momentum into a ranked at-risk list, a Monday morning briefing delivers it to your inbox, and chasing stalled onboardings with context sends re-engagement nudges that reference what's actually open. The full playbook for acting on falling engagement is in how to catch stalled onboardings before they churn, and the wider AI use-case library shows more of these agent workflows.
Bring both levels into one view
The two engagement levels only give you a full picture when they live side by side. The practical move is to pipe your product activity into the same place your process data already lives, so you see onboarding progress and actual product adoption per account without switching tools.
You can push activation events in from Mixpanel, PostHog, or Amplitude via Zapier or Make, the API, or Valuecase's MCP – one of the few onboarding platforms with one, which lets AI tools read and act on onboarding context directly. And because engagement and progress sync two-way to HubSpot and Salesforce, onboarding health sits right next to the account record in your CRM – no double entry, no stalls hiding in the gap between "tasks done" and "product used." Running the whole thing as a shared project with the customer is covered in managing onboarding projects together with clients.
FAQ
How do you measure onboarding engagement?
Measure it on two levels. Process engagement is whether the customer is working through the onboarding itself – opening the shared plan, completing tasks and forms, showing up to calls – tracked automatically as activity and an engagement score per customer workspace. Product engagement is whether they're actually using your product, tracked as activation events in a tool like Mixpanel or PostHog. Watch both, because a customer can be active in one and silent in the other.
What onboarding metrics matter?
The leading indicators are workspace engagement (is the customer showing up?), task and form completion against the plan, and meeting cadence. Alongside those, track outcome metrics like time to value, activation rate, and completion rate. Engagement predicts the outcome, so it's the one to act on weekly – see our onboarding metrics and KPIs guide for the full set.
How do you know if a customer is engaged?
An engaged customer keeps opening their onboarding materials, moves through tasks without being chased, responds in the workspace, and keeps scheduled calls – and, for software products, logs in and takes key actions. The clearest warning signs are the opposite: a workspace not opened in a week, engagement that drops sharply after kickoff, a stakeholder who never appears, or a repeatedly postponed check-in.
Want to see engagement tracking on every customer onboarding in one place? Book a demo and we'll show you how it works.
