Feature adoption answers a single question: are users actually using the feature I shipped? In Amplitude, you track adoption by measuring exposure, activation, and retention—then watching where users drop off. Without this data, you're guessing whether your feature matters.
How Feature Adoption Works in Amplitude
Adoption isn't binary. Users move through stages: they see the feature (exposure), try it once (activation), use it again (engagement), and eventually either stick around or abandon it (retention). Amplitude's Funnel chart lets you see where each group drops off.
Track the activation event
When a user tries your feature for the first time, send an activation event. Include the feature name and how they discovered it. This becomes the baseline for your adoption calculations.
amplitude.track('Feature Activated', {
'feature_name': 'dark_mode',
'discovery_method': 'settings_menu',
'timestamp': Date.now()
});Build a funnel to see adoption drop-off
In Amplitude, go to Analyze > Funnel. Add three steps: Feature Exposed, Feature Activated, Feature Engaged. This shows what percentage of exposed users activate, and what percentage of activated users engage again. If 50% activate but only 15% engage a second time, adoption is stalling.
// Track repeat engagement to measure adoption stickiness
amplitude.track('Feature Engaged', {
'feature_name': 'dark_mode',
'interaction_count': 3,
'days_since_activation': 2
});feature_name property. It lets you measure adoption for multiple features in one dashboard without rewriting code.Measuring True Adoption with Retention
Activation is a vanity metric. Real adoption is measured by how many users come back to use the feature 7 days, 14 days, and 30 days later. Amplitude's retention chart shows this curve.
Use the Retention chart to track long-term adoption
Go to Analyze > Retention. Set the starting event to your activation event. Measure 'Return Event' as feature engagement. If 40% of users return on day 1, 20% on day 7, and 5% on day 30, you know adoption is declining sharply. Fix this by improving the feature's value or making it easier to access.
// Set user cohort properties for adoption segmentation
amplitude.setUserProperties({
'feature_flag_variant': 'control',
'user_segment': 'power_user',
'signup_date': '2024-03-01'
});
// Track engagement within a specific session
amplitude.track('Feature Engaged', {
'feature_name': 'dark_mode',
'session_length_ms': 2400,
'variant': 'control'
});Segment adoption by user type
Click Add Property on any retention chart. Segment by plan type, signup cohort, or user region. Enterprise users might adopt at 70% while free users adopt at 15%. This gap tells you whether the feature is positioned correctly for your audience.
// Track adoption metrics segmented by user plan
const userPlan = getUserPlan(userId);
amplitude.track('Feature Activated', {
'feature_name': 'advanced_reporting',
'user_plan': userPlan, // 'free', 'pro', 'enterprise'
'plan_tier_numeric': ['free', 'pro', 'enterprise'].indexOf(userPlan)
});Calculating Adoption Rates You Should Track
Not all adoption metrics matter equally. Focus on these three to understand whether your feature is actually being used.
Calculate DAU adoption (daily active user adoption)
Go to Insights > User Totals to get daily active users. Create a chart showing daily feature events. Divide daily feature users by total DAU. If 25% of your DAU uses the feature daily, adoption is solid. If 3%, the feature is niche or failing to gain traction.
// Track daily feature engagement with context
if (userUsedFeatureToday) {
amplitude.track('Daily Active Feature User', {
'feature_name': 'dark_mode',
'dau_segment': calculateUserSegment(userId),
'device_type': getDeviceType()
});
}Measure D-7 and D-30 adoption rates
In Amplitude, create a new chart. Event: Feature Activated. Filter to users who also had a Feature Engaged event 7 days later. This shows what percentage of users who activate actually return. Most features see 30-50% D-7 adoption; below 20% is a red flag.
// Track with time-based adoption windows
const activationDate = new Date();
const daysSinceActivation = Math.floor((Date.now() - activationDate) / (1000 * 60 * 60 * 24));
amplitude.track('Feature Engagement Check', {
'feature_name': 'dark_mode',
'adoption_window': daysSinceActivation > 7 ? 'd7_plus' : daysSinceActivation > 30 ? 'd30_plus' : 'early',
'is_repeat_user': daysSinceActivation > 0
});Common Pitfalls
- Confusing page views with adoption. A user visiting the settings page isn't adopting a feature until they actually enable it. Track the action, not the navigation.
- Measuring adoption too early. Features need 7-14 days to stabilize. If you check on day 1, you're measuring marketing noise, not real adoption.
- Ignoring churn. 70% activation with 20% D-30 retention is worse than 40% activation with 35% D-30 retention. Focus on the retention gap, not just the activation rate.
- Not segmenting by user type. Enterprise and free-tier users adopt at vastly different rates. A blanket adoption metric hides where your feature is failing.
Wrapping Up
Feature adoption in Amplitude is built on tracking three stages: exposure (feature exists), activation (first use), and retention (they came back). Use funnels to find drop-off, retention charts to measure stickiness, and segmentation to understand which user types adopt. If adoption is stuck below 30% on day 7, your feature isn't discovering its value. If you want to track this automatically across tools, Product Analyst can help.