Feature Adoption
Feature adoption is the extent to which users discover, start using and keep using a specific product feature. It is usually measured as the share of eligible or active users who use the feature in a period, and is often called feature usage. Low adoption tends to point to a discoverability or value problem rather than a missing feature, which makes it a key check after every launch.
How Feature Adoption Works
The most common formula is:
Feature adoption rate = Users who used the feature in period / Eligible active users in the same period x 100
"Eligible" matters. If only paid plans include a feature, free users should not be in the denominator. "Used" also needs a clear definition: completing the feature's core action, such as sending a scheduled report, rather than just opening its page. Getting both right depends on reliable event tracking.
Pendo breaks adoption into four dimensions:
- Breadth: how widely the feature is adopted across the user base or a target segment.
- Depth: how often key users use it, and whether they use it as intended.
- Time to adopt: how long it takes users to start using a new feature.
- Duration: how long users keep using it after they first try it.
Adoption also works as a small funnel: users must notice the feature, try it once, and then come back to it. Each step can fail for a different reason.
Why Feature Adoption Matters
Shipping a feature is not the same as delivering value. Tracking adoption keeps teams out of the "feature factory" trap, where success means releasing things rather than changing user behavior. Building more on top of a feature nobody uses rarely helps.
Adoption data guides roadmap decisions: invest further in features that are widely and repeatedly used, fix the entry point or the experience of features with strong interest but poor follow-through, and consider retiring features that few people use but that still cost effort to maintain. Comparing retention between users who adopt a feature and those who do not hints at which features matter most, although that comparison alone does not prove the feature causes users to stay. For using these signals in planning, see how growth managers use usage metrics to inform feature roadmaps.
Feature Adoption Example
A reporting tool launches scheduled exports, available on its Team plan. In the first 30 days, 4,000 Team users create at least one report, which makes them eligible. Of those, 600 set up a schedule, a breadth of 15%. In the following month, 420 of the 600 still have an active schedule, showing good duration among those who found it.
Interviews reveal that most users never noticed the option, which sat in a settings menu. The team moves the entry point onto the report page and tracks whether breadth rises while duration holds steady.
Feature Adoption vs. Activation
Activation is about a new user reaching the product's core value for the first time, usually in their first days. Feature adoption applies to any specific feature at any point in the customer's life, including advanced features that only experienced users need. A product can have strong activation and still have many features with poor adoption.