Post Your Build Ideas
Launch

Activation Rate: Definition, Formula and How to Pick Your Activation Event

Activation rate is the share of new signups who reach the first moment where your product visibly works for them, within a time window you set. You divide the signups who performed the activation event by all signups in the same group. It sits between getting a signup and keeping a user, and it is usually where a young product loses most of its people.

What does activation rate actually measure?

A signup proves interest. Activation proves that the interest turned into an experience. The two can be far apart: someone can create an account, look at an empty dashboard and never return, and you would count them in your signups for ever. Activation rate is the number that separates those people from the ones who got something done.

The formula is simple. Pick a cohort, for instance everyone who signed up during launch week. Count how many performed the activation event within a fixed window after signing up, such as 24 hours. Divide the second number by the first. A different window or event gives a different rate, so record both beside the figure.

Illustrative example: a shared shopping-list app, launch week cohort
MeasureCount
Signups in the cohort40
Created a list31
Added an item to a list24
Invited another person to the list (the activation event)12
Activation rate within 48 hours12 of 40, which is 30%

The counts are invented to show the shape. Each row is a step a person must pass, and the drop between rows shows where to look. Here the biggest loss is between adding an item and inviting someone, which hints that the product’s value, sharing, is introduced too late.

How do you choose the activation event?

The event should be an action that shows value was delivered, not one that shows the user was present. Logging in, verifying an email and opening the app all fail that test. Ask what your most enthusiastic early users did in their first session that the rest did not. Interview or watch five people and look for the first action after which they said “oh, that is useful”.

  • Shared list app: a second person joins a list, because the product exists to coordinate.
  • Resume checker: a first score is generated for an uploaded file.
  • Metrics dashboard: the first real data source connects and the first chart shows real numbers.
  • Habit tracker: a habit is logged on a second day, because one tap on day one proves nothing.

Write the definition and the window before launch and do not move them afterwards. Changing the event after you see disappointing numbers produces a rate that goes up and a product that did not change.

How do you track it when you have only a few users?

You do not need event tracking at first. Keep a spreadsheet with one row per signup, the signup time, the date of the activation event if any and a note. Fill it from your database or admin screen once a day. With forty rows the rate is obvious, and the notes column is where the learning is: “asked how to import”, “tried on a phone and gave up”.

Add a short, human message to every signup who has not activated after a day. “Did you get stuck anywhere?” sent by hand to ten people teaches more than a funnel chart. Replies become your onboarding fixes, and the onboarding email sequence template gives wording for the first two messages. When you do get to automate, the same event definition carries over.

How is it different from conversion, retention and time to value?

Conversion rate is about getting the signup: visitors who became people with accounts. Activation is about what those people then do. Retention rate is about whether they keep coming back after that first success. Time to value measures how long the journey to the activation event took, for the people who made it. The same event feeds two of these: the share who reached it is activation, the elapsed time is time to value.

That relationship suggests an order of work. Fix visits to signups only after people who do sign up are getting value. Sending more traffic into a leaky onboarding wastes the traffic you worked hardest for. When you launch your product free, the first hundred visitors are the most expensive you will have, so make sure the first session works.

What are the common pitfalls?

  • Calling signup the activation. Then the rate is 100% and tells you nothing.
  • Picking an event too deep. If only paying power users ever reach it, the rate will be near zero for everyone and give no direction.
  • Mixing cohorts. The launch-day crowd and a quiet fortnight later are different groups. Track them separately.
  • Ignoring the people who never activate. Those are the majority of your learning. Ask them one question.

Because your product’s value is specific, so is the event. Look at productivity ideas to see how makers phrase a first result, and run your onboarding past a few testers before launch using how to get feedback on an MVP.

Frequently asked questions

What is a good activation rate?

No honest figure applies to every product. Rates depend on how you define the event, how hard the product is to start using and who arrives. Compare your own cohorts over time with the same definition and window, and treat a sustained rise after a specific change as the useful signal.

How is activation rate calculated?

Take all signups in a cohort, count those who performed the activation event within your chosen window, and divide the second by the first. If 12 of 40 people invited a second person within 48 hours, activation is 30%. Record the event and window next to the number so later comparisons are fair.

What counts as an activation event?

An action that shows the product delivered value, such as sending a first invoice, getting a first score or connecting a data source. It should not be an action that merely shows presence, like logging in. Look at what your happiest early users did first, then confirm it by watching a few new users.

Do I need an analytics tool to track activation?

Not at the start. A spreadsheet with a row per signup and a yes or no for the event works with a few dozen users and gives better notes than a dashboard. Add tooling when manual tracking takes more time than the learning is worth, and keep the same definition.

Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.