Benchmarks for PLG activation rates are all over the internet, and most of them are misleading. You'll see figures like "top PLG products achieve 40-60% activation" printed confidently in blog posts and investor decks, without a definition of what "activation" means in those numbers or what product categories they cover.
We spent a few months working closely with the early-stage PLG teams in our beta cohort, helping them instrument activation funnels and establish baselines. This post shares what we learned about what realistic benchmarks look like, why the popular numbers are usually wrong, and how to build a comparison that's actually useful for your product.
Why published benchmarks are often useless
The core problem with activation rate benchmarks is denominator ambiguity. What counts as a user in your activation rate calculation? Signups who verified their email? Signups who logged in at least once? Signups who completed the first onboarding step? These definitions can produce wildly different numbers from the same product data.
A PLG product that counts "verified email" as the denominator will show lower activation rates than one that counts "completed first login." Both definitions are defensible. Neither is more correct. But you can't compare them as if they mean the same thing.
The same ambiguity applies to the numerator. If your activation event is "user viewed the dashboard," your activation rate will look much higher than if your activation event is "user completed a meaningful workflow." Products that optimize for soft activation events can report high rates while quietly losing users who never did anything useful with the product.
Before you benchmark yourself against any published number, you need to know exactly what definition that number used. If the source doesn't provide it, the benchmark is not usable.
What we saw in the beta cohort
Across the early-stage PLG products in our beta cohort, we saw a wide range of activation rates once they were measured consistently against meaningful value events. Without disclosing any specific product's numbers, here's the distributional shape we observed.
Products with the simplest setup paths and immediate value delivery tended to activate 30-50% of signups against a real value event definition within the first two sessions. Products with complex setup requirements or features that only become useful after significant configuration activated a much smaller proportion in that early window, sometimes in the 10-20% range, with the remaining users either churning or activating slowly over weeks.
Neither of these ranges is "good" or "bad" in isolation. A product with a complex setup curve and a 15% early activation rate might be building a much better retention moat than a simple product with a 45% rate, because the users who do activate are investing enough to stay. Context matters enormously.
What was consistent across the cohort: teams that tracked activation against a meaningful value event made better product decisions than teams that tracked against soft events. The meaningful-event tracking led to specific onboarding changes. The soft-event tracking mostly led to teams feeling good about their numbers while their 60-day retention lagged.
The setup complexity penalty
One pattern we saw clearly: every setup step between account creation and the first value event costs you activation rate. This sounds obvious, but the magnitude surprised us.
We looked at products that required connecting an external data source before showing any useful output. The proportion of users who reached the value event after completing the integration step was high, often above 60%. But the proportion of total signups who completed the integration step was much lower, in the 20-35% range for most products. The integration step was the primary activation bottleneck, not the product itself.
This suggests a common structural opportunity: optimizing the integration step or finding a way to deliver preliminary value before it. For some products, this means sample data that lets users see what the product looks like before they've connected their real data. For others, it means redesigning the integration flow to be substantially faster.
We're not saying you should remove required setup steps that are genuinely necessary. We're saying the cost of each required step is higher than most teams intuit, and quantifying that cost is the first step to deciding which steps deserve optimization investment.
Segment-specific activation rates tell a cleaner story
One of the most consistent findings in our cohort work: product-level activation rates are noisy because they mix segments that activate on very different timelines.
Consider a PLG product where one group of users signs up with a specific job-to-be-done in mind (say, an analyst who heard about the product from a colleague), and another group signs up out of general curiosity (someone who saw a social post). These two users are likely to have very different time-to-value curves and very different probability of eventually activating. Averaging their activation rates together tells you almost nothing actionable.
The teams in our cohort that made the most progress on activation did it by segmenting their activation analysis. Once they could see that their high-intent signup segment was activating at over 50% while their low-intent segment was below 10%, they could make targeted decisions: invest in improving the activation flow for the high-intent group (high ROI), investigate whether the low-intent group represents real product fit or acquisition noise, and stop blaming the product for aggregate numbers driven by segment mix.
How to build your own benchmark
If you want a benchmark that's actually useful for your product, the process is internal, not external. Here's the logic we use with products in our cohort.
First, define your activation event precisely. This is the moment the user has gotten the specific value your product exists to deliver. Not "they completed the setup." Not "they returned to the product a second time." The actual value moment.
Second, measure the activation rate against that event for three consecutive 30-day cohorts of signups. This gives you a baseline that accounts for seasonal variation and pipeline changes. You're not comparing yourself against industry numbers. You're establishing your own baseline.
Third, segment by user type or job-to-be-done. Break the aggregate number into at least two meaningful sub-groups and track them separately from day one. This is the number you'll improve against.
Fourth, identify the highest-dropout step in the funnel from signup to activation. That step is where you focus your next onboarding iteration. Fix it, remeasure, and repeat.
External benchmarks can serve one purpose: directional sanity checks. If your meaningful-event activation rate is consistently below 5% for a high-intent segment, that's a signal worth investigating regardless of where you'd like your number to be. If you're above 40% for a segment with complex setup requirements, you've probably built a genuinely strong onboarding path and should understand what's driving it.
What a realistic good looks like by maturity stage
We'll offer some directional ranges, with the explicit caveat that these are based on our observations of early-stage PLG products and should not be treated as industry standards.
For a product in early growth with a relatively simple setup path and a clearly scoped value event, activating 30-45% of high-intent signups against a real value event within the first two sessions is a reasonable sign of a functional onboarding path. Below 20% in that segment suggests the onboarding path has a material structural problem worth finding.
For products with complex integration requirements, those numbers shift down. Activating 20-35% of high-intent signups who complete the integration step is reasonable. The more important number to watch is how many signups actually reach the integration step, and that's where the optimization work usually belongs.
For products that require multi-user collaboration before value is visible, early activation rates will be lower, and time-to-value will be measured in days rather than hours. That's expected and not a product failure. The benchmark to watch is activation rate among accounts where at least one invite was sent, compared to accounts where no invite was sent. That comparison will almost always show the product's real activation potential.
The meta-point about benchmarks is this: the number that tells you whether your activation is working is the one that correlates with the retention outcome you care about. For most PLG products, that's 60-day or 90-day paid conversion. Build the benchmark that predicts that outcome for your specific product. That benchmark will be more useful than any industry percentile published by someone who doesn't know your value event definition.