Quick answer
Product adoption is the process by which users move from learning a product exists to using it as a regular part of their routine. Measure it with three signals: they used it, they used it again, and it became a habit.
Formula: User adoption rate = users meeting the habit rule ÷ users who signed up in the period. Feature adoption rate = users who used the feature N+ times ÷ users who could use it. Stickiness = DAU ÷ MAU.
What is product adoption?
Product adoption is the process by which a person goes from learning that a product exists to using it as a regular part of how they work or live. Amplitude describes it as the journey from introducing a product to it becoming a regular, essential part of users' routines; Mixpanel adds that adoption requires users to reach a successful outcome and form a habit, which separates it from simply acquiring a user.
The word is used at two scales, and it helps to keep them apart. At the market level, adoption describes how a whole population takes up a new product over time; that is the technology adoption curve. At the user level, which this page covers, it describes what one person does after signing up: do they use the product, use it again, and keep using it? A related question, feature adoption, asks the same of one capability inside the product. For a worked guide with benchmarks to chase, see how to measure product adoption and feature adoption; this page is the definition and the arithmetic.
Stages of product adoption
Amplitude lays adoption out as five stages: awareness, interest, evaluation, trial and adoption. The first three happen mostly before the product is touched, in marketing and sales. Once someone is inside the product, three behavioural signals are easier to measure than a stage label:
| Signal | Question | How to write it as a rule | Related term |
|---|---|---|---|
| Used | Did they reach the first moment of value? | Did the key action at least once within 7 days of signup | Activation rate |
| Used again | Did they come back and repeat it? | Did the key action on 3 or more different days within 14 days | Early retention |
| Became a habit | Is it part of their routine? | Active in 3 of the 4 weeks after the first month | Sustained retention, stickiness |
The thresholds above are examples. What matters is that each signal is written as an event, a count and a time window, so two people computing it get the same answer. Pick the key action as the one that delivers the product's value, not the one that is easiest to count; the aha moment and time to value pages explain how to find it.
Adoption, activation, engagement and retention: how they differ
| Term | What it measures | Typical window | Denominator |
|---|---|---|---|
| Activation | Reached first value | First days after signup | New signups |
| Adoption | Made the product a routine | Weeks to months | New signups (user level) or active users (feature level) |
| Engagement | How often and how much they use it | A day, week or month | Active users |
| Retention | Whether they are still active later | Day N or week N | The starting cohort |
Activation is the first rung and retention is the evidence, while adoption is the claim you make from both: "these users made this product part of their routine." Engagement describes intensity and can be high for a month and then fall off, which is why it does not prove adoption on its own.
How to calculate adoption rates
Neither Amplitude's nor Mixpanel's overview prints a single formula, so write down your own. Three that work in practice:
- User adoption rate = users who met the "habit" rule ÷ users who signed up in the same period.
- Feature adoption rate = users who used the feature at least N times in a window ÷ users who had the chance to use it. Count the denominator carefully: dividing by all signups understates adoption for a feature that only appears after setup.
- Stickiness = daily active users ÷ monthly active users, the DAU / MAU ratio Mixpanel mentions as a stickiness measure.
Worked example: 2,000 signups, three signals
Sample data: 2,000 people signed up in January. For each, we check the three rules above.
| Step | Rule | Users | Rate vs previous step | Rate vs all signups |
|---|---|---|---|---|
| Signed up | In the January cohort | 2,000 | — | 100% |
| Used | Key action within 7 days | 1,100 | 55.0% | 55.0% |
| Used again | Key action on 3+ days within 14 days | 560 | 560 ÷ 1,100 = 50.9% | 28.0% |
| Habit | Active in 3 of the 4 weeks after month one | 330 | 330 ÷ 560 = 58.9% | 16.5% |
Overall user adoption is 330 ÷ 2,000 = 16.5%. The loss is spread over three steps, but the biggest absolute drop is the first one (900 people never reached value), while the weakest step in relative terms is the second (only half of those who used it came back). The two problems need different fixes, which a single "adoption rate" would hide.
Now the feature level, using the 1,100 users who reached first value as the denominator:
| Feature | Users who used it 2+ times in 30 days | Feature adoption rate |
|---|---|---|
| Dashboards | 980 | 980 ÷ 1,100 = 89.1% |
| Export | 330 | 330 ÷ 1,100 = 30.0% |
| Alerts | 154 | 154 ÷ 1,100 = 14.0% |
| Sharing | 88 | 88 ÷ 1,100 = 8.0% |
Dashboards are the core habit. Alerts and sharing sit at 14% and 8%: either they serve a smaller group, or most people never found them. Compare users who did adopt alerts with those who did not on retention before deciding which it is.
Common mistakes
- Counting logins as adoption. Opening the product is not using it. Tie adoption to the action that delivers value.
- Using the wrong denominator. Feature adoption divided by all signups punishes features that only exist for configured accounts; divide by users who could use it.
- Judging too early. A habit needs weeks. A rate measured at day 7 describes activation, not adoption.
- Averaging across very different users. A blended rate hides that one plan or channel adopts at 30% and another at 5%. Split by segment before concluding.
- Reading a high-adoption feature as a good one. A feature everyone must pass through, such as sign-in settings, will show high use without delivering value.
- Assuming a tour or tooltip caused it. Users who finish a tour are the motivated ones. Check against a comparison group before crediting it.
Measuring product adoption in TapCub
Take the January cohort above. A product team could set it up in TapCub like this.
- Send the key action as an event. Call
tapcub.trackfor the action that delivers value, for examplecreate_report, and list it in All-platform analytics › Data › Tracking plan so the team agrees on its meaning. - Count who did it. In All-platform analytics › Behavior › Behavior analysis, chart the event by unique users for the January signups, and use a funnel from signup to the key action to see the 55% step.
- Check who comes back. Use retention in the same place to see how many of the cohort are active in week 2, 3 and 4; the lifecycle view labels people New, Returning, Resurrecting or Dormant.
- Split the habit group out. Build a rule segment in All-platform analytics › Users › Segments & tags, for example "did create_report 3+ times in 30 days", then compare it with everyone else.
- Watch stickiness. TapCub's active-user metrics give the daily and monthly counts you need for DAU / MAU.
TapCub measures adoption; it does not build product tours, run feature flags or send in-app surveys. Whatever you change to raise adoption, do it with your own tools and use TapCub to see whether the three signals moved.
Sources
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Technical Engineer
Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.