Why Most PLG Companies Miss Their Own Activation Benchmark

The median B2B SaaS product activates roughly 37 out of every 100 users who sign up. The best-performing PLG products activate 70 or more. Most founders who look at that gap assume it is a product problem — the onboarding needs more tooltips, the UX needs simplifying, the value proposition needs sharpening. In most cases, that diagnosis is wrong. The gap between 37% and 70% is almost entirely a measurement problem: teams that hit 70% have defined activation correctly; teams sitting at 37% have defined it wrong, measured the wrong proxy, and optimized for a number that does not predict retention.

What the activation rate actually measures

Activation rate measures the percentage of new users who reach a predefined behavioral milestone within a specific time window after signup. The definition sounds straightforward, but the milestone is where most teams go wrong. The most common definitions are "completed onboarding checklist," "logged in three times in the first week," or "set up their first project." None of these definitions are activation events. They are activity proxies — they measure engagement effort, not value delivery.

A true activation event is the moment a user experiences the core value your product is built to deliver. In a project management tool, it might be the first time a user collaborates with a teammate on a task. In an analytics product, it might be the first time a user creates and shares a dashboard that surfaces an actionable insight. In a billing tool, it might be the first recurring payment processed successfully. The definition is product-specific because the value is product-specific — and the only way to identify it accurately is to validate behavioral candidates against retention data from real users.

The measurement failure: why teams track logins instead of value

The majority of PLG companies that fall in the 30-40% activation range use activity metrics as activation proxies because activity is easy to measure and value delivery is harder to define. Session counts, login frequency, and feature touch events all require nothing more than basic analytics instrumentation. Defining the value moment requires running a cohort analysis on converted vs churned users, identifying behavioral discriminators, and committing to a specific threshold — a process that takes longer and surfaces uncomfortable conclusions about what the product actually needs to deliver.

The consequence of proxy-based activation definitions is that teams optimize for the wrong thing. They add more onboarding steps, gamify checklist completion, and push notification campaigns that drive logins — and then watch their activation number tick up without any corresponding improvement in 90-day retention or conversion to paid. The number moves because the proxy moved; the underlying metric — whether users are experiencing real value — does not. According to the UserGuiding State of PLG 2026 report, only 34% of PLG companies actively track activation as a defined metric at all — most track activity and call it activation.

What the 70% cohort instruments differently

Products that consistently hit 70%+ activation share a common instrumentation pattern. They have run cohort analysis on converted vs churned user cohorts and identified specific behavioral sequences that predict retention. Their activation event is a verb-noun action — not a checklist completion, but something like "report.shared," "integration.connected," or "collaborator.invited" — that fires at the moment a user crosses from product exploration into product dependence.

The difference between exploring and depending is the core distinction most activation definitions miss. A user who explores the product but does not connect it to their actual workflow will churn. A user who connects the product to a real workflow — who has data flowing, a team member notified, or a report embedded in their regular decision-making process — has converted their relationship with the product from trial to dependency. That dependency moment is what the 70% cohort has identified and instrumented. The time-to-value instrumentation guide covers how to set up the event tracking infrastructure to capture this moment; this post is about how to identify which moment to capture.

How to identify your real activation event

The method is a cohort analysis on 90 days of historical user data. Take all users who signed up in a given period and split them into two cohorts: those who converted to paid (or retained for 90+ days in a freemium model) and those who churned. Pull every event both cohorts fired in their first 7 days. Sort the events by the ratio of converted users who fired the event to churned users who fired the same event — you are looking for events where the converted/churned ratio is 2x or higher.

That ratio list gives you activation candidates. The strongest candidates are events that: (1) have a conversion lift of 2x or more, (2) are fired by at least 40% of eventual converters (high recall), and (3) occur within the first 3 days of signup for the majority of converters (early enough to influence with product or messaging interventions). Run this analysis across 2-3 separate 90-day cohorts to confirm the behavioral signal is stable across cohorts and not an artifact of a specific acquisition channel or product change. Once validated, the activation event becomes a derived server-side event that fires automatically when a user's behavioral history crosses the threshold — not a manual tag that requires someone to click something.

The instrumentation gap that creates the 37% floor

Most SaaS products sitting below 50% activation have a common technical gap: their event tracking captures actions but not outcomes. They track "user clicked report builder" but not "user created report with at least one live data source." They track "user invited teammate" but not "teammate accepted and completed first action." The action events exist in their analytics; the outcome events do not, because outcome events require more instrumentation thought — they are often composite signals derived from multiple events rather than single user actions.

Closing the instrumentation gap requires adding what the event taxonomy framework calls outcome events: server-side derived events that fire when a meaningful business outcome is achieved, not when a UI element is clicked. These events require access to server-side data (whether the invited user accepted, whether the report has live data, whether the integration pulled successfully) that client-side JavaScript cannot determine. The products with 70%+ activation rates have this instrumentation in place; the products at 37% are typically tracking only what their front-end can see.

Building activation rate into your product analytics stack

Once the activation event is defined and instrumented, the activation rate becomes a weekly product metric alongside conversion and retention. The most useful view is a 7-day rolling activation rate by acquisition cohort — not overall activation rate, which blends cohorts from different acquisition channels and time periods into a number that is hard to act on. Cohort-level activation rate shows which channels are sending users who activate and which are sending users who do not, which is the information needed to make acquisition and onboarding decisions.

The activation rate also becomes the north star for onboarding optimization. With a clearly defined activation event, every onboarding intervention — email sequences, in-app guidance, sales touchpoints — can be A/B tested against a single outcome: did the user reach the activation event, and did they reach it faster? This gives onboarding optimization the same experimental rigor as ad creative testing or pricing page testing. Teams with properly instrumented activation events run activation experiments the same way they run conversion experiments; teams without them are guessing. The activation gap benchmarks break down what the top quartile specifically does with those experiments once the infrastructure is in place.

What happens after activation: the retention and expansion link

The reason activation rate is the right north star metric for PLG companies is not that activation is the end goal — it is that activation is the strongest leading indicator for the metrics that actually drive SaaS business value. Mixpanel's 2026 PLG guide puts it plainly: "activation is the leading indicator for retention, expansion, and revenue" — meaning the metrics that determine SaaS company health are downstream of activation quality.

The data supports the claim. Users who activate retain at dramatically higher rates than users who do not, and the retention gap compounds over time. An activated user who retains for 90 days has a significantly higher probability of expanding to a higher plan, adding seats, or becoming a reference customer — none of which is available from a user who explored the product for a week and churned. The expansion revenue analytics framework covers how to instrument and measure the activation-to-expansion pipeline once the activation event is correctly defined. The starting point is always the activation definition itself — which is why the 37% to 70% gap, in most cases, begins and ends with how the activation event was specified.