Users sign up but do not activate. Where is your onboarding breaking?

Answer in 60 seconds

If users create an account but do not use the product, do not begin by adding tooltips or extending welcome sequences.

First:

• define the user, job and context you are analysing;
• name the observable event that demonstrates first meaningful value;
• verify that the event and cohort denominator are measured correctly;
• find where users stop between expectation, access, setup, first task and useful result;
• combine behavioural data with interviews, observation and support evidence;
• test the smallest justified change on a bounded cohort.

Signup, login, onboarding completion and activation are different events. A user can complete every onboarding screen without achieving the outcome they came for.

There is no universal “good activation rate”. The useful rate depends on the product, eligible population, value event, time window and acquisition context.

In this guide

• 1. Define activation as demonstrated value
• 2. Validate the event and the denominator
• 3. Locate the first break in the journey
• 4. Redesign the shortest credible path to value
• 5. Choose measurement, onboarding, product or human support

1. Define activation as demonstrated value

Start with a sentence:

For this user in this context, activation means completing this meaningful task and receiving this useful result within this relevant period.

The event should represent evidence of value, not evidence that your interface was displayed. “Viewed the tour” may describe exposure. “Invited a colleague” or “published the first page” may be closer to value when that action matters to the user.

Learn the need before choosing the milestone. GOV.UK’s service guidance recommends using analytics, search logs and support data alongside interviews and observation to understand who users are and what they are trying to do. It also warns that suggestions from people who are not users are assumptions to investigate, not user needs (GOV.UK).

Treat activation as an operational definition, not a universal product metric.

2. Validate the event and the denominator

Before redesigning onboarding, check:

1. Who entered the cohort: every account, eligible users, invited users or verified humans?
2. When does the clock start: registration, invitation acceptance or first eligible session?
3. Does the event fire once, repeatedly or before the task succeeds?
4. Are internal users, tests, bots, duplicates and failed imports excluded?
5. Can you reconcile product events with account and support records?
6. Are web, mobile and regional journeys measured consistently?

Benchmarks can help you ask questions, but they cannot define your target. Amplitude’s 2025 Product Benchmark Report analysed customer-product data from September 2023 to September 2024 and reported that 69% of products in the top quartile for seven-day activation were also in the top quartile for three-month retention (Amplitude).

That is a correlation in a vendor dataset, not proof that pushing one activation event will cause retention. Instrumentation, product mix, customer selection and opt-outs limit transferability.

3. Locate the first break in the journey

Use one cohort and trace the path:

Do not force one explanation onto every segment. A founder arriving from a referral, an employee invited into a team and a buyer evaluating a trial may have different tasks and stopping points.

A systematic review of 147 articles on information-system continuance grouped antecedents into psychological, technological, social and behavioural factors and highlighted an intention–behaviour gap (International Journal of Information Management). It supports a multi-factor investigation, not a SaaS activation formula.

Prediction is not explanation either. A 2023 digital-health study found that first-seven-day login patterns could help predict early dropout in four smoking-related interventions, with model performance varying across interventions (JMIR). The population and products are not a general SaaS benchmark, and predictive association does not prove why a user left.

4. Redesign the shortest credible path to value

Once the break is observed, remove work that does not protect the user, service or result.

• Ask only for information needed at that point.
• Explain why a permission, connection or configuration matters.
• Provide realistic sample data where empty states block understanding.
• Preserve progress when users leave or encounter an error.
• Put contextual help beside the decision, not in a detached feature tour.
• Offer a human route when setup carries commercial, technical or organisational risk.

Authentication can itself block activation. W3C’s guidance for accessible authentication explains that users should not be required to complete a cognitive-function test unless an alternative or assisting mechanism is available; support for password managers and copy-and-paste can reduce burden (W3C).

That guidance addresses a specific WCAG success criterion. It does not establish full accessibility conformity, and client-specific assessment still requires qualified review.

5. Choose measurement, onboarding, product or human support

A professional activation review should leave a segment definition, event dictionary, reconciled cohort, observed journey, evidence register, prioritised hypotheses and measurement plan.

Conclusion: the next sensible move

Onboarding is not the number of screens between signup and the dashboard.

Define the first meaningful result. Verify who had a fair opportunity to reach it. Observe the point where the journey stops, then repair the smallest defensible part of the system.

Frequently asked questions