Feature adoption rate is the percentage of eligible users who use a feature within a defined time window. The formula is: (Users who used the feature / Total eligible users) x 100. Eligible means users who have access to the feature, not your entire user base.
The Three Metrics That Matter
Adoption rate: What percentage discovered and tried the feature. Measured at Day 7 and Day 30 after launch. Day-7 catches initial interest. Day-30 catches sustained adoption.
Activation rate: What percentage completed the full workflow. Trying a feature is not adopting it. If your feature is a report builder, adoption means viewing the page. Activation means building and saving a report.
Retention rate: What percentage came back to use it again. A feature used once and abandoned is not adopted. Track weekly return rate for the first 8 weeks after a user first tries it.
Use the Feature Adoption Calculator to compute these rates and benchmark them against industry norms.
Setting Targets
Realistic adoption targets depend on feature type:
Core workflow features (things users came to your product to do): Target 60-80% adoption within 30 days of availability. If below 40%, you have a discovery or usability problem.
Enhancement features (improvements to existing workflows): Target 30-50% adoption. Not every user needs every enhancement.
New capability features (expanding into adjacent use cases): Target 15-30% adoption. These serve a subset of your user base by design.
Diagnosing Low Adoption
If adoption is low, work through this diagnostic tree:
Discovery problem: Users do not know the feature exists. Check how many users viewed the feature entry point (menu item, button, page). If fewer than 50% of eligible users even saw the entry point, invest in in-app announcements, tooltips, or email campaigns.
Usability problem: Users find the feature but do not complete the workflow. Check the drop-off funnel. Where do users abandon? Simplify the flow. Reduce steps. Add defaults.
Value problem: Users complete the workflow but do not return. The feature does not solve a real problem or solves it poorly. Go back to discovery. Run user interviews. The assumption mapper can help identify which value assumptions failed.
Tracking Setup
Instrument three events per feature:
- Feature viewed (discovery): User saw the feature entry point
- Feature started (adoption): User began the core workflow
- Feature completed (activation): User finished the core workflow
Track these with user ID, timestamp, and feature version. Cohort the data by user signup date to distinguish new user adoption from existing user adoption. The NPS Calculator provides complementary satisfaction data to pair with adoption metrics.
The prioritization guide explains how to use adoption data as input for your next quarter's roadmap decisions.