> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/intelligence/heart/adoption.md).
# Adoption
What the Adoption dimension measures, how its three metrics work, and what the expected user count controls.
Adoption is the HEART[^1] dimension that measures whether the licensed user base shows up, engages meaningfully, and keeps engaging over time.
## What Adoption measures
Adoption answers three questions about an application:
* How many of the expected users actively use it?
* Are users meaningfully engaged, or logging in without doing much?
* Are users keeping up their engagement, or starting to drop off?
Adoption measures who uses the application. Efficiency measures the speed and consistency of task completions. Task Success measures whether tasks complete. The three are related but score different things.
The Adoption dimension detail in the HEART scorecard.
## How the score is calculated
The Adoption score combines three metrics, each on a scale of 0 to 100: license utilization, engaged user rate, and user persistence.
When no expected user count is entered, license utilization is inactive and the score reflects engaged user rate and user persistence only. Any metric without enough data is left out rather than scored as zero.
When Adoption is inactive entirely, HEART handles it as described in [How the score is calculated](/intelligence/heart.md#how-the-score-is-calculated).
## What feeds the score
### License utilization
Active users divided by the expected user count, as a percentage. The expected user count is a number your organization enters in the portal: how many users you expect to actively use the application.
### Engaged user rate
The share of users with at least one engaged session in the scoring period.
An engaged session means real interaction with the application, not a passing visit or an idle tab. Userlane uses fixed thresholds for duration and activity to separate genuine use from incidental logins and tab switches. The thresholds are not configurable.
### User persistence
The share of engaged users who keep up their usual engagement frequency.
A user counts toward persistence only after building up enough history. Users with less history are left out of the calculation entirely. Each user's recent engagement is compared with their own past pattern, not with other users.
One limitation: users with very irregular patterns or very low activity may not show as disengaging, because their normal variation is too wide to register a drop.
### Activation
Engaged user rate and user persistence activate automatically once the application has enough data over a sufficient period. License utilization also needs the expected user count.
## Relevant articles
{% content-ref url="/pages/TBF4QYHDMWQghy26u8xI" %}
[HEART](/intelligence/heart.md)
{% endcontent-ref %}
{% content-ref url="/pages/wHkexeXXbTSpfCo6v7UR" %}
[Portfolio Overview](/visibility/portfolio-overview.md)
{% endcontent-ref %}
{% content-ref url="/pages/rZlpzz2pdmo3sBhYdyH1" %}
[App Discovery](/visibility/app-discovery.md)
{% endcontent-ref %}
{% content-ref url="/pages/H0TpAAVoypgUSRX7TiLj" %}
[Efficiency](/intelligence/heart/efficiency.md)
{% endcontent-ref %}
## FAQ
What happens if the expected user count is not entered?
License utilization is left out of the Adoption score. The score reflects engaged user rate and user persistence.
What counts as an engaged session?
A session with real interaction: enough duration and activity to show genuine use rather than an incidental login or tab switch. The thresholds are fixed and not configurable.
What is Adoption measured against?
License utilization and user persistence are measured against your own data. Engaged user rate uses fixed thresholds, so it stays consistent over time and across applications.
Can the engaged session thresholds be changed?
No. The thresholds are fixed so scores stay comparable.
[^1]: HEART is Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.userlane.com/intelligence/heart/adoption.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
