Activation

What is Activation?

Activation is the first moment a new user experiences your product's core value, the step between signup and real retention.

The term comes from Dave McClure's "Pirate Metrics" framework, AARRR: Acquisition, Activation, Retention, Referral, Revenue. McClure laid it out in a deck called "Startup Metrics for Pirates," where he defines Activation as the stage where users "enjoy 1st visit" and get a "happy user experience," and he proposes rough activation criteria: 10-30+ seconds on site, 2-3+ page views, 3-5+ clicks, and use of one key feature. McClure introduced the framework in a talk at Ignite Seattle. The surviving public decks carry no fixed timestamp of their own, so the exact date of that talk isn't pinned down here, only the content, which is well established.

Activation stuck around because it forces a specific question. Not "did the user sign up" but "did the user do the thing that predicts they'll stay." PostHog frames the practical test the same way, asking simply whether new users actually use the product, while cautioning against treating the AARRR order as a literal sequence teams must move through step by step.

Why it matters for product-market fit

Produck's loop is Listen, Diagnose, Decide, Ship. Activation is where Listen and Diagnose meet. If you only Listen to feedback from users who never activated, you're optimizing for people who barely touched the product, and you'll ship features that don't move retention at all. Diagnose has to separate "this user churned before activating" from "this user activated and still churned," because those are two different problems with two different fixes.

We wrote about this gap directly in why the PMF stack is broken: most teams collect feedback and NPS scores without ever tying them back to whether the person giving feedback actually reached the aha moment. An activated user's complaint and a never-activated user's complaint should never sit in the same bucket during Decide.

Activation is also a natural input to your North Star Metric. If your North Star is a retention-driven number like weekly active teams, your activation rate is a leading indicator for it, moving before the North Star itself does. Watching activation move gives Decide something to act on before the North Star shifts, which is the whole point of tracking a metric upstream of the outcome you actually care about.

When it works, and when it doesn't

It works when

• The activation event is something a user does, not something you do to them, like sending a welcome email or granting a trial extension.
• You've validated the activation event actually correlates with long-term retention in your own data, not copied from another company's blog post.

It falls short when

• The activation event is set too early, like "created an account," so nearly everyone hits it and it stops predicting anything.
• The activation event is set too late, like "used the product for 30 days," so it can't function as an early warning signal at all.
• Teams treat activation rate as a vanity number to report upward instead of a lever to pull on in the product.
• Nobody revisits the activation definition as the product changes, so it quietly stops matching what actually predicts retention.

How to apply it

1. Pull your last 90 days of signups and separate them into users who stuck around past 30 or 60 days and users who churned.
2. Look at what the retained group did in their first session or first week that the churned group didn't.
3. Pick one candidate action as your activation event and set a rough threshold, like the number of times or how quickly it happened.
4. Instrument that event cleanly so you can see, for every new signup, whether and when they hit it.
5. Route feedback and support tickets through Listen and tag each one with whether that user had activated, so Diagnose can weight signal from activated users differently.
6. Revisit the activation definition every quarter as your onboarding and core feature set change.

activation vs onboarding

Onboarding is what you build. Activation is what you measure. Onboarding is the screens and setup steps you design to walk a new user toward value. Activation is the outcome you're checking for, whether that user actually reached value, regardless of which onboarding path got them there. A great onboarding flow that never gets anyone to the activation event has failed, and a clunky onboarding flow that reliably gets users to activate is still doing its job.