Product Adoption Rate: Formula and Examples

Product adoption rate is the percentage of eligible users who adopt your product in a given period, and the formula is: product adoption rate = (users who completed the adoption event in the period ÷ users who were eligible to adopt in the period) × 100. If 1,200 people signed up for your product in October and 420 of them completed the adoption event within 30 days, the product adoption rate for the October cohort is 420 ÷ 1,200 × 100 = 35 percent.

TL;DR

• Product adoption rate = adopted users ÷ eligible users × 100. Both counts come from the same period and the same population.
• The number only means something once you define the adoption event (what a user has to do to count as adopted) and the window (how long they have to do it).
• Analytics vendors define the metric differently. As of November 2026, Pendo publishes a feature adoption formula based on monthly logins, Mixpanel's Impact report divides adopters by adopters plus non-adopters, and Pendo's Product Engagement Score uses the average number of core events adopted.
• There is no reliable universal benchmark. Compare cohorts against your own earlier cohorts and against your own segments.
• Product adoption rate, activation rate and feature adoption rate are three different metrics. This post shows the formula for each.

What is product adoption rate?

Product adoption rate measures how many of the users who could adopt your product actually did, within a set time. It is a share, not a count, so it lets you compare a month with 500 signups against a month with 5,000. It is a lagging metric: it tells you whether the onboarding, the first-run experience and the product itself turned a signup into a user who gets value.

The word "adopt" is where most teams go wrong. A login is not adoption. A single click on a feature is not adoption. Adoption means the user has done the thing your product exists to do, usually more than once. Amplitude's glossary defines adoption rate as "the percentage of users who have adopted your product out of the total number of users" (as of November 2026), which is the right shape, but it leaves "adopted" for you to define. The next two sections do that.

What is the product adoption rate formula?

The formula has two inputs and both need a precise definition before you calculate anything.

• Numerator: adopted users. The number of users who completed your adoption event inside the measurement window. Count each user once, even if they completed the event ten times.
• Denominator: eligible users. The number of users who had the chance to adopt in the same window. For a new-user view, this is the signup cohort. For an installed-base view, it is every active user or every licensed seat in the period.
• Window. A fixed number of days after the user becomes eligible (for cohorts) or a calendar period (for the installed base). Use the same window every time or the trend is meaningless.

Written out: product adoption rate (%) = adopted users ÷ eligible users × 100.

Two rules keep the number honest. First, numerator and denominator must come from the same population: do not divide October adopters by September signups. Second, pick one of the two views (new-user cohort or installed base) and label the metric accordingly, because the two can move in opposite directions in the same month.

How do you define the adoption event?

The adoption event is the action, or short sequence of actions, that shows a user has started getting the product's core value. It should pass four tests: it is the core workflow rather than a setup step, it is observable in your analytics, it happens early enough to measure within your window, and users who do it retain better than users who do not. The last test is the one that matters; check it against your own retention data before you commit.

Examples of adoption events by product type:

• Project management tool: created a project and completed at least three tasks in it.
• Analytics product: connected a data source and viewed a saved report on two separate days.
• Billing software: sent a real invoice to a customer (not a test invoice).
• Customer support platform: connected an inbox and resolved ten conversations.
• Internal CRM rollout (IT view): logged an activity or updated a record in each of two consecutive weeks.

Notice that most of these include repetition or a real-world consequence. A single action is usually activation, which is covered below.

Product adoption rate examples

Three worked examples, one for each way the metric is commonly used.

Example 1: new-user cohort adoption

A B2B SaaS product gets 1,200 signups in October. The adoption event is "created a workspace and invited at least one teammate who accepted", and the window is 30 days from signup. By November 30, 420 of the 1,200 have done it.

Product adoption rate (October cohort, 30 days) = 420 ÷ 1,200 × 100 = 35 percent.

The September cohort, measured the same way, was 31 percent. The number went up, and because the window and the event are fixed, the comparison is valid.

Example 2: feature adoption rate

The same product ships a reporting feature. In November, 8,000 users logged in and 1,360 of them used the new reports.

Feature adoption rate (November) = 1,360 ÷ 8,000 × 100 = 17 percent.

This matches the formula Pendo publishes for the metric. As of November 2026, Pendo's feature adoption glossary entry states "Monthly Feature Adoption Rate (%) = [feature MAU / monthly logins] * 100". The denominator is logins in the month, not total accounts, so dormant users do not drag the rate down. Our post on what feature adoption is covers how to set targets per feature instead of one target for the whole product.

Example 3: account-level adoption

For B2B contracts, the user is often the wrong unit. A customer success team sells 50 seats to an account; adoption of the account is what predicts renewal. Suppose the account has 50 licensed seats and, in the last 30 days, 32 of those seats completed the adoption event.

Account adoption rate (30 days) = 32 ÷ 50 × 100 = 64 percent.

Roll this up across the book of business as a weighted average (total adopted seats ÷ total licensed seats) rather than an average of percentages, or a ten-seat account at 100 percent will mask a 500-seat account at 20 percent.

How do analytics tools calculate adoption rate?

If you use a product analytics tool, its built-in adoption metric may not match the formula above, so check the definition before you put a number in a board deck. Three documented examples, all checked in November 2026:

• Mixpanel, Impact report. Mixpanel's documentation defines adopters as users who triggered a launch event and states that "the Adoption Rate is the number of users who perform the launch event divided by the total user count", where the total is adopters plus non-adopters who performed a chosen metric event. This is a feature-launch view: the population is users active on the metric event, not all signups.
• Pendo, feature adoption. The glossary formula quoted above, feature MAU divided by monthly logins, times 100.
• Pendo, Product Engagement Score. Pendo's PES page describes the adoption component as "the average number of Core Events adopted across all active Visitors or Accounts". That is an average count of events per user, not a percentage of users, so it is not directly comparable to a product adoption rate.

The practical point: when two teams in the same company report different adoption numbers, the cause is almost always a different numerator, denominator or window, not a different reality. Write the definition next to the number every time.

What is a good product adoption rate?

There is no universal benchmark worth publishing. Adoption rate depends on the adoption event you chose, the window, whether the product is self-serve or sales-led, and whether the denominator is a signup cohort or an installed base. A 35 percent cohort rate with a demanding event can be excellent; a 70 percent rate with a trivial event can hide a retention problem. Vendor benchmark reports are collected under the vendor's own definitions, so treat any figure you find as context, not a target.

Better comparisons are internal: this month's cohort against the last six cohorts; enterprise accounts against mid-market accounts; users who came through a sales demo against users who came through a free trial. If the segmented rates differ by more than a few points, you have found where to work.

Product adoption rate vs activation rate vs feature adoption rate

These three are often used interchangeably and should not be.

• Activation rate = users who reached the first-value moment ÷ new signups × 100. It is about the first session or first week. Our activation rate guide walks through defining the activation event and fixing the biggest drop-off.
• Product adoption rate = users who made the core workflow part of how they work ÷ eligible users × 100. It comes after activation and usually requires repetition.
• Feature adoption rate = users who used one specific feature ÷ users who could have (typically monthly logins) × 100. It is measured per feature.

Time to value is a fourth, related metric and it is a duration, not a share: how long it takes a user to reach the first-value moment.

How do you improve product adoption rate?

Once the formula is in place, the rate moves for a small number of reasons: users do not know the core workflow exists, they get stuck part-way through it, they finish it once and have no reason to repeat it, or the wrong people were counted as eligible in the first place. Work through those in order.

• Check the denominator first. Remove test accounts, internal users and duplicate signups. A dirty denominator understates adoption more often than any product problem.
• Map the path to the adoption event and find the single step with the largest drop-off. Fix that step before adding guidance anywhere else.
• Answer the user at the step where they stop. Most users who abandon a workflow had a question they could not answer in the moment. An in-app agent such as Worknet answers from your documentation and the user's own account context, and can take the next step for them with permission, so the question does not become a dropped workflow or a support ticket.
• Give the event a reason to repeat. A weekly report, a notification tied to real activity, or a teammate invitation turns a one-time win into a habit.
• Segment the rate by plan, acquisition channel and role, and review it in the same weekly meeting as retention. Adoption that is not reviewed does not move.

What is Worknet?

Worknet is an AI adoption agent for the software your customers use and the software your employees use. It sits with every user inside the app, offering proactive support and onboarding. It answers with context, acts on the user's behalf within the permissions you set, and brings in the right person from your team when needed. For SaaS companies, what it learns becomes expansion signals for sales, risk alerts for success, and fixes for product. For IT, it rolls out across the apps you buy with no vendor changes and shows where employees get stuck. An AI-native alternative to Pendo, WalkMe and Appcues.

For the metric in this post, the useful part is the signal. When the agent sees where users stop inside the core workflow, those stopping points are the drop-offs that hold your adoption rate down, and they reach the product team as fixes rather than as a line on a dashboard.