> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/adoption.md).

# Adoption

The Adoption page helps service managers, application owners, and end-user computing teams track the deployment of a brand new application, existing software rolled out to a new country, or a specific new feature recently added through an upgrade. Additionally, it allows you to track the license usage ratio in order to help identify cost optimization opportunities and highlight compliance issues.

The information gathered by Nexthink Applications enables the management of an application roadmap and life-cycle by giving insights into how the business service is used and what features are accessed the most.

<figure><img src="/files/xVq9VhRuQmVhAVQXsXcg" alt=""><figcaption></figcaption></figure>

The charts help you quickly identify patterns impacting the employee experience.

## Adoption metrics <a href="#adoption-adoptionmetrics" id="adoption-adoptionmetrics"></a>

Filter usage by browser, operating system, location, or other options. Refer to [Configuring geolocation](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/administration/system-configuration/product-configuration.md) documentation for more information about the geolocation feature.

### Employees <a href="#adoption-employees" id="adoption-employees"></a>

Employees represent the total number of unique employees who have had a focus on the application, which means they were in the browser tab of the app at least once, resulting in a usage time higher than 0.

This number can be different from the number of employees in speed page loads for a number of reasons:

* Speed page loads counts employees with at least one page load, whereas the Employee metric counts when a user focuses on a browser tab even if they haven’t navigated to it. This can occur when the tab was opened outside of the given timeframe.
* Users can navigate to a page without focusing on it if the page opens in the background.
* Speed page loads retrieves only hard navigations as soft navigations are not taken into account, whereas the Employees metric takes into account both soft and hard navigations.

For each point on the line graph, we display the sum of unique employees whose usage time is higher than 0 during a given time bucket. Therefore, the sum of all the values on the line chart should always be equal to or higher than the KPI value.

### Usage time per employee <a href="#adoption-usagetimeperemployee" id="adoption-usagetimeperemployee"></a>

This dashboard shows the average usage time or focus time per user for a given timeframe selected in the dashboard. Usage time includes both page load time and the time the employee is not interacting with the page at all, as long as the tab is focused. It is the sum of all focused usage times across all users in a given timeframe, divided by the number of distinct users.

On the line graph, each drawn point is the average usage time per user, computed for all unique active users of a given time bucket: 15 min, 1 hour, 1 day ...

### Page views per employee <a href="#adoption-pageviewsperemployee" id="adoption-pageviewsperemployee"></a>

This dashboard shows the average number of navigations per user for a given timeframe. Both hard and soft navigations are taken into account. 

On the line graph, each point is an average number of navigations per user, computed for all unique active users in a given time bucket: 15 min, 1 hour, 1 day ...  Unlike in a breakdown, all page navigations are counted and not only those that are currently registered as key pages. This way, the shape of the curve does not change for the previous period, even if some key pages no longer exist.

***

RELATED TASKS

* [Speed](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/speed.md)
* [Reliability](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/reliability-old-experience.md)
* [Troubleshoot](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/troubleshoot.md)
* [Monitoring capabilities](/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/diagnostics-for-web-applications.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/~/changes/Sh4xqs4GDClkDKT9Hvux/user-guide/applications/monitoring-applications/monitoring-web-applications-old-experience/adoption.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.