Ask five people on a SaaS team what "activated" means and you may get five answers: completed the profile, invited a teammate, finished the tour, logged in twice, connected an integration. Each one gives a different activation rate, and most of them can go up while retention stays flat.
Before you work on raising activation, the whole team needs one definition. This guide covers how to choose it, how to measure it and how to tell whether your onboarding changes it. For tactics to raise the number once you have it, see how to increase SaaS activation.
What an activation metric is
An activation metric is one action, done within a set time after signup, that people who stay tend to do and people who leave tend not to. It is the first time someone gets the value they signed up for, often called the aha moment, written down precisely enough to count.
The rate itself is simple: of the people who signed up in a given week, the share who did that action within the window. Measure it by signup cohort, not as a running total, so a good week or a big launch doesn't hide a bad trend.
Step 1: list the actions that deliver value
Start with what people pay you for, not with your onboarding steps. Write down five to ten actions that mean someone got real value. For example:
- An invoicing tool: sent the first invoice to a real client.
- A scheduling tool: received the first booking.
- An analytics tool: built a dashboard and shared it with a colleague.
- A team chat tool: three or more people from one company sent messages.
Leave out anything that is only a step towards value. Creating an account, filling in a profile and finishing a tour all come before the value, so they make poor activation metrics.
Step 2: check which one predicts retention
Take people who signed up a few months ago and split them into those who are still active and those who left. For each candidate action, compare how many in each group did it in their first week or two. The action that best separates the two groups is your strongest candidate. Most product analytics tools can show this as a retention report split by a first-week event.
You are looking for a good separator, not a perfect one. If almost everyone who stayed did the action and few of those who left did, that is enough to work with.
Step 3: pick the time window
Match the window to how often your product is naturally used. For a tool people open every day, one to three days is fair. For something used weekly, seven to fourteen. For monthly work such as invoicing or payroll, you may need thirty. Too short, and you undercount people who are slow but fine. Too long, and the metric takes a month to tell you anything.
Step 4: test the definition
- It is something the user does, not something you do to them. "Received the welcome email" is not activation.
- It is reachable within the window. If hardly anyone reaches it in the first week, it is a later milestone.
- It is one action, with a count if it needs one: "created 3 projects", not "is engaged".
- Different roles may need different metrics. The admin who sets up the account and the colleagues they invite get value in different ways. Measure them separately rather than averaging them.
Why tour completion is not activation
Onboarding tools make it easy to report tour completion and checklist progress, and those numbers are useful for fixing the tour itself. But a completed tour measures the tour. People can click Next five times and never do the thing the tour was about. If onboarding works, the activation metric moves, not just the completion rate.
Step 5: prove onboarding moves it
The honest way to know whether a tour or a checklist helps is to hold some people back and compare them with the people who saw it. Otherwise you can't tell whether the tour caused the result, or whether the people who finish tours were going to activate anyway.
In Cueston, that takes two settings on a tour, tooltip or banner:
- A goal. Success means the person does your activation event in your app, visits a page or completes other content, within 1 to 30 days of seeing the item.
- A holdout. Up to 50% of the people who match don't see the item at all, and they become the control group.
The item's analytics page then shows goal conversion for each group, the difference, and whether it is statistically significant at 95% confidence. Until enough people have been through it, it tells you how many more it needs. Once you are convinced, set the holdout back to 0 so everyone gets the guidance.
Your app reports the event to Cueston with one line of code:
Cueston.track('Invoice sent')The same event can do more work. It can tick off a checklist item, and audience rules can target people who did it fewer than some number of times in recent days, or not at all. That puts help in front of the people who haven't activated yet and leaves everyone else alone. The JavaScript API has the details.
Mistakes that make the number meaningless
- Changing the definition every quarter, so no trend line survives.
- Picking the event that is easiest to move rather than the one that predicts retention.
- Reporting one blended rate across every role and plan.
- Counting a running total instead of signup cohorts.
- Celebrating a jump in tour completion as if it were activation.
Frequently asked questions
What is a good activation rate?▾
It depends on the product and, above all, on how you define activation, so published benchmarks rarely compare like with like. The most useful comparison is your own earlier cohorts under the same definition.
What is the difference between activation and onboarding?▾
Onboarding is what you do to help new users get started: tours, checklists, emails. Activation is the result you want from it, the user reaching real value for the first time. You judge onboarding by whether activation goes up.
How is an activation metric different from the aha moment?▾
The aha moment is the experience of getting value. The activation metric is the action you count as a sign that it happened, with a time window, so that you can measure it.
Can I measure activation without engineering?▾
If your app already sends the event to Cueston, yes. If not, a developer adds one Cueston.track call for it. A page visit, such as reaching a success page, also works as a goal with no code at all.