Blog · Board and management reporting · Software
An adoption dashboard compares qualifying usage, feature uptake, and later return activity. This worked software example starts with exported user rows, proves the cohort totals, and changes one input to show what moves.
An adoption dashboard compares active users, feature uptake, and later retention using the same eligible population and clear observation windows. It should show the counts behind every percentage. A rising activity count can reflect more eligible users rather than stronger adoption.
For a software business, choose an action that represents useful work. In this example, a user is active after completing an approval workflow. The feature is a shared approval template, and feature uptake means using that template in a completed workflow.
Group users by the month they first become enabled. The cohort entry rule and the later return rule need separate definitions, as the cohort exploration documentation explains. This example measures first-week activity during elapsed days 0 through 6, followed by return activity during days 28 through 34.
The dashboard concerns software use. Adoption by purchase cohort examines investment holdings after purchase and uses a different business population. Keep those questions separate even though both involve cohorts.
An illustrative US software company, Mesa Workflow, reviews its customer-user cohorts on April 1, 2026. January users became enabled January 1 and February users became enabled February 1. All return windows are complete, and every user shown is entitled to use the template feature.
The supplied exports contain user ID, enabled date, account ID, qualifying action date, and feature name. Summarize them into one row per user. A Yes flag means at least one qualifying action within the named window; repeated events do not add users.
| User | Enabled cohort | Active in days 0–6 | Template used in days 0–6 | Active in days 28–34 |
|---|---|---|---|---|
| J1 | January | Yes | Yes | Yes |
| J2 | January | Yes | Yes | Yes |
| J3 | January | Yes | No | Yes |
| J4 | January | Yes | No | No |
| J5 | January | No | No | No |
| F1 | February | Yes | Yes | Yes |
| F2 | February | Yes | No | Yes |
| F3 | February | Yes | No | No |
| F4 | February | No | No | No |
| F5 | February | No | No | No |
Retain the event dates behind each flag for review. Exclude staff and test accounts using the same documented rule in both cohorts. When one person has several identifiers, resolve that mapping before counting unique users.
First-week active rate = Users active in days 0–6 / Enabled users
Feature uptake among active users = Template users in days 0–6 / Users active in days 0–6
Cohort retention = Users active in days 28–34 / Enabled users
| Dashboard measure | January calculation | January result | February calculation | February result |
|---|---|---|---|---|
| Enabled users | Count January rows | 5 | Count February rows | 5 |
| First-week active users | J1, J2, J3, J4 | 4 | F1, F2, F3 | 3 |
| First-week active rate | 4 / 5 | 80.0% | 3 / 5 | 60.0% |
| Template uptake among active users | 2 / 4 | 50.0% | 1 / 3 | 33.3% |
| Template reach among enabled users | 2 / 5 | 40.0% | 1 / 5 | 20.0% |
| Retained users | J1, J2, J3 | 3 | F1, F2 | 2 |
| Cohort retention | 3 / 5 | 60.0% | 2 / 5 | 40.0% |
Percentages are rounded to one decimal place. The feature rows answer different questions: reach across the enabled population and uptake among people already active. Put the denominator in the dashboard label so neither rate can be mistaken for the other.
The SaaS onboarding KPIs article covers activation timing and setup milestones. Use those measures to investigate how users reached this view without turning the adoption dashboard into an onboarding checklist.
January has four active users plus one inactive user, equal to five enabled users. February has three active plus two inactive, also equal to five. Every template user is included in the first-week active population because template use requires a completed workflow.
Across the cohorts, enabled users total 5 + 5 = 10. Active users total 4 + 3 = 7, giving 7 / 10 = 70.0%. Template users total 2 + 1 = 3, so combined uptake among active users is 3 / 7 = 42.9%; reach among enabled users is 3 / 10 = 30.0%.
Retained users total 3 + 2 = 5, giving 5 / 10 = 50.0%. These totals come from distinct users, not action counts. Retention calculation guidance explains distinct-user counting and why unfinished periods require separate treatment.
Now suppose a corrected export shows F3 completed a qualifying workflow during days 28 through 34. Change only that return flag from No to Yes; first-week activity and template use remain unchanged.
| Measure | Original February | Corrected February |
|---|---|---|
| Enabled users | 5 | 5 |
| First-week active users | 3 | 3 |
| Template users | 1 | 1 |
| Retained users | 2 | 3 |
| Cohort retention | 2 / 5 = 40.0% | 3 / 5 = 60.0% |
Combined retained users rise from five to six, and combined retention becomes 6 / 10 = 60.0%. February's retention changes by 20.0 percentage points because one user changes in a small cohort. Feature uptake does not move, so this correction cannot support a claim that feature usage improved.
The product manager owns the qualifying actions and the question behind each card. Customer success can review inactive users within customer accounts. The reporting owner reconciles users to the enabled register and confirms that the exported dates cover every window.
Review the inactive February users and ask whether they had the right access, training, and need for the workflow. Keep customer-level conclusions separate: several users can belong to one account. B2B product KPIs connect account adoption with commercial retention and recurring value.
Bring a sample of your own enabled-user register and usage export to Covirage; it maps the columns, and its tools compute cohort counts, uptake, retention, and reconciliation checks. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your file.
See self-service analytics with Covirage for the supporting context.
Include eligible users, users completing the qualifying action, feature users, and retained users by cohort. Show each numerator and denominator, the observation windows, and the report cutoff. Add context such as customer segment only when it helps someone decide what to investigate.
It can be, if access is the behavior you need to measure. For product value, choose an action that reflects completed work and label it clearly. Avoid switching between logins and completed work across periods, because the resulting rates answer different questions.
It depends on the question. Divide feature users by eligible users to measure reach across the entitled population. Divide feature users by active users to measure uptake among participants. Report the denominator explicitly and keep feature eligibility consistent within the comparison.
Match the review cadence to the product's expected use and the decision it supports. A frequent operational review can track activity, while retention comparisons need complete observation windows. Keep unfinished cohort results pending instead of presenting partial counts as final performance.