Product Adoption Depth
Also known as: Feature Penetration, Module Utilization
The percentage of licensed features, modules, or capabilities that a customer is actively using. Unlike basic adoption rate which may just track logins, adoption depth measures how deeply customers engage with the full product surface.
Formula
(Features/modules actively used / Total features/modules available in customer’s plan) × 100 Who Is This Metric For?
Identify underutilized features in accounts and create enablement plans to deepen adoption.
Track adoption depth trends across the portfolio to inform training and enablement strategy.
Understand which features customers adopt and which they ignore to inform product roadmap.
Use adoption depth as an expansion readiness signal — deeply adopted customers are prime upsell candidates.
Priority by Stage
Track basic product usage first (logins, active users). Feature-level tracking can wait.
Define what 'active use' means for each key feature. Start tracking adoption depth for top-tier accounts.
Adoption depth should be a health score input and expansion indicator. Low depth = at-risk; high depth = expansion-ready.
Use adoption depth for predictive modeling. Identify features that most predict retention and steer customers toward them.
Benchmarks
| Segment | Good | Great | World Class |
|---|---|---|---|
| Low Complexity | 50-60% | 60-75% | 75%+ |
| Moderate Complexity | 35-50% | 50-65% | 65%+ |
| High Complexity | 25-40% | 40-55% | 55%+ |
Common Mistakes
- Treating all features equally — some features are core, others are nice-to-have
- Not adjusting expectations by plan tier — a customer on a basic plan shouldn’t be measured against enterprise features
- Measuring adoption without context of use case — a customer may not need every feature to get value
- Ignoring adoption velocity — how quickly customers adopt features matters as much as total adoption