A product adoption KPI is fair when it measures breadth you can influence, such as seats activated or teams onboarded, and unfair when it measures depth the roadmap controls. Pick one definition, write it down, and measure it per account against that account's own licence count. The most useful version is the licence gap: seats paid for minus seats used.
A product adoption KPI puts a CSM in an awkward position: the number moves when customers change their behaviour, and customers change their behaviour when the product is worth changing for. Some of that is your work and some of it is the roadmap. The way through is to define adoption narrowly enough that the part you own is the part being measured.
This page separates the three definitions that get called adoption, gives the one number that lands with executives on both sides, sets realistic targets, and covers the case where usage data does not exist at all. That last case is common enough to have its own thread: one CSM working with public sector customers on air-gapped systems described active users and utilisation as unavailable, with self-reported metrics unreliable.
- Three different things get called adoption: breadth (how many users), depth (how many features) and frequency (how often). A CSM can move breadth and frequency; depth usually belongs to product.
- Measure against the account's own licence count, not against a company-wide average. A 60% adoption target means something different on a 12-seat account and a 400-seat one.
- The licence gap is the number executives respond to: seats paid for minus seats used, priced. It converts an adoption problem into a renewal risk in one line.
- In-app guidance decays fast with length. Median product tour completion was 29% in the first half of 2026, and completion fell from 73% for one to two step tours to 8% for tours of nine steps or more (Produktly, 2026).
- If you cannot see usage at all, on-premise or air-gapped deployments included, switch the KPI to a proxy the customer will report: named users trained, workflows live, or a quarterly self-reported count.
Questions this page answers
- is product adoption a fair kpi for a csm
- how do i measure adoption when i cannot see usage data
- what is a realistic adoption rate target for b2b saas
- how do i increase licence utilisation before renewal
- adoption breadth vs depth vs frequency which should we measure
- how do i move an adoption number i do not control
Which definition of adoption is my KPI using?
Ask this before agreeing to any target. Three definitions circulate, they move independently, and a CSM can influence two of them.
| Definition | Measures | Who moves it | Fair as a CSM KPI? |
|---|---|---|---|
| Breadth | How many licensed users are active | CSM, through enablement and onboarding | Yes |
| Depth | How many core features an account uses | Product and roadmap, with CSM influence | Partly |
| Frequency | How often active users return | Product design and workflow fit | Partly |
| Outcome adoption | Whether the workflow the customer bought is live | CSM, jointly with the customer | Yes, and the most useful |
The licence gap is the number of seats a customer pays for minus the number they use, priced at their per-seat rate. It turns adoption from a percentage nobody acts on into a dollar figure a buyer recognises, and it is the version of the metric that survives a renewal conversation. A 40-seat account using 14 seats is not an adoption statistic, it is 26 seats of renewal risk.
Adoption rate = Active users in the period ÷ Licensed seats × 100
- Active users
- users who performed a core action, not users who logged in. Logins measure curiosity
- Licensed seats
- what the contract says, per account. Never a company-wide average
- Licence gap
- (Licensed seats − Active users) × Price per seat. The same fact, in the unit a buyer thinks in
What is a realistic product adoption KPI target?
Set it from your own installed base rather than from a benchmark, because adoption rates depend on how the product is sold. Products sold top-down with bulk seats start low; products sold to the team that uses them start high.
Take the last four quarters of accounts that renewed
Ignore the ones that churned for now. You are looking for the adoption level that is compatible with a renewal, not the ideal.
Find the 25th percentile of their adoption rate
That is your floor: the level below which renewals get difficult. It is usually lower than anyone expects and it is the honest starting target.
Find the median of accounts that expanded
That is your stretch: the level associated with growth rather than survival. The gap between the two numbers is the range worth managing.
Set the target per segment, not per book
Enterprise bulk-seat deals and small self-serve teams should not carry the same number, and averaging them produces a target that is wrong for both.
Review the definition every quarter
New plans, new features and new pricing change what a seat means. A target set against last year's packaging measures the packaging.
For the activation side of the same question, on new accounts rather than the installed base, see how to improve product adoption in the first 30 days, which covers the published activation metrics nine named companies use.
Does in-app guidance move an adoption KPI?
It moves it a little, and less than the length of most tours assumes. Benchmarks from the first half of 2026 show completion falling sharply with every added step, which is the single most actionable finding for a CSM asked to raise adoption with the tools already in the product.
| Tour length | Median completion | Tours measured |
|---|---|---|
| 1 to 2 steps | 73% | 45 |
| 3 to 5 steps | 38% | 65 |
| 6 to 8 steps | 25% | 84 |
| 9 or more steps | 8% | 62 |
Two more numbers from the same dataset are worth carrying into a conversation with product: overall median tour completion was 29%, and user-initiated tours completed at a 69% median against 23% for auto-started ones. If adoption is your KPI and the product team is adding an eleven-step onboarding tour, this is the evidence for a shorter one that the user asks for.
What if I cannot see usage data at all?
Then measure something the customer will tell you, and make reporting it part of the relationship rather than an extra request. On-premise, air-gapped and privacy-restricted deployments are the obvious cases, but the same approach works when instrumentation does not exist yet.
- Named users trained, counted from your own session records rather than from the product
- Workflows live, agreed with the customer at kickoff and confirmed at each review
- Self-reported active user count, asked for once a quarter in the same format so the series is comparable
- Support and request volume per account, which correlates with use and is visible on your side
- Configuration milestones completed, which you can see because your team did them
“Most systems are air-gapped (no connection to the internet), and asking the customer to report metrics is unreliable. Using metrics like active users, utilization, and time/milestones to adoption aren't stable across accounts”
When the data cannot exist, say so in writing and propose the proxy set above as the KPI. A target built on numbers nobody can produce fails at review time regardless of the work done underneath it.
How do I move an adoption number in one quarter?
Work the licence gap on your largest accounts, in that order. Breadth moves faster than depth because it needs people rather than features.
The quarter plan
- Rank accounts by licence gap in dollars, largest first, and take the top ten
- For each, find who was licensed and never activated, by name, from the customer's own admin
- Ask the admin for one thing: a 20-minute session with the unactivated group, scheduled by them
- Run the session on their data, on one workflow, ending with each person having done it once
- Re-measure at 14 days and report the gap closed in seats and in dollars
Worked example
A book of 60 accounts has 4,100 licensed seats and 2,050 active users, so 50% adoption. The top ten accounts by licence gap hold 900 of the 2,050 unused seats. Ten sessions across a quarter activate 320 of them, which moves book adoption from 50% to 58% and closes about $190,000 of licence gap at a $600 per seat annual price. The other 50 accounts were not touched, and the number still moved eight points.
How does GainTrace report adoption per account?
GainTrace reads product usage alongside billing, so licensed seats and active users sit on the same record and the licence gap is a number rather than a spreadsheet exercise. Product signals tracks depth and trend rather than logins, and flags the accounts whose adoption is falling against their own baseline, which is the group where a renewal conversation is coming.
Frequently asked questions
Is product adoption a fair KPI for a CSM?
What is a good adoption rate for B2B SaaS?
How do I measure adoption without product analytics?
What is the licence gap?
Do product tours improve adoption?
Should adoption or retention be the CSM's primary KPI?
How this was researched
In-app guidance benchmarks are from Produktly's SaaS Onboarding and In-App Engagement Benchmarks 2026, built from anonymised aggregated data across 464 companies and 15.8 million tracked interactions between January and June 2026; tour completion figures come from 88 companies with 100 or more users starting tours, and the length breakdown from 256 tours with 50 or more starts each. The definitions table, the licence gap framing and the quarter plan are ours. The measurement-constrained case comes from r/CustomerSuccess threads on public sector and air-gapped deployments, quoted verbatim.
- Produktly: SaaS Onboarding and In-App Engagement Benchmarks 2026
- r/CustomerSuccess: Customer success KPIs in the public sector
- r/CustomerSuccess: Difference between CSM and account manager
- r/CustomerSuccess: Adoption workflows that scale versus ones that look good in a deck
- Benchmarkit: 2025 B2B SaaS Performance Metrics Benchmarks (retention context)
Rank your accounts by licence gap this week, then work the top ten. Start free or book a demo.
See GainTrace first in your Google results
Add as a preferredsource on Google