> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/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/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/adoption.md).

# Adoption

The **Adoption** tab focuses on active users and their usage behavior to understand how employees use an application, identify adoption gaps, and improve engagement.

## Explore overall adoption trends

The top section of the **Adoption** tab visualizes how application adoption evolves over time. The system calculates these metrics from the `web.events` [NQL table](https://docs.nexthink.com/platform/understanding-key-data-platform-concepts/nql-data-model#web_event). The adoption metrics are based on active application usage, not on the total number of app-licensed users.

Arrow indicators help you quickly identify, using red and green color conventions, whether adoption trends are higher or lower compared to the previous 30-day period.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FJXYn4ZLX60jhPHD4E5IC%2F2026.8_AppEx_9_N5tYv1.png?alt=media&#x26;token=86eb0f38-c7cd-4e01-99b5-cb23d1a0d5f2" alt=""><figcaption></figcaption></figure>

From the **Adoption** tab of the target application:

* Hover the **Employees** bar chart to see how many employees use the application over the last 30 days.
* Check **Usage time / employee / day** to evaluate how users engage with the application on a daily basis.
* Correlate **Employees** and **Usage time / employee / day** metrics to identify patterns:
  * Growth in employees indicates expanding adoption.
  * A stable number of employees with decreasing usage time suggests decreasing engagement.
  * Overall declining trends may indicate performance issues or a lack of adoption.
* Look for irregular trends and changes that may reflect rollout phases or seasonal usage.
* Hover over the **Employees** metric to open the **action menu** and drill down into usage time for the underlying employees. Specific employee identities are not shown, in line with privacy rules.

{% hint style="info" %}
The system calculates adoption metrics over a **rolling 30-day period**. Trend charts show how this 30-day usage evolves over time and may aggregate data for readability.
{% endhint %}

## Analyze adoption distribution across employee groups and application features

Examine the heatmap to understand how adoption varies across your organization groups, and within the target application itself.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FwLIKProiLiloOiSFIu1i%2F2026.8_AppEx_10_Q8mZx6.png?alt=media&#x26;token=1e303138-fe0c-4a0f-9a44-1f203696547e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **Total by** column represents unique users and may not equal the sum of all cells. When datasets are large, the heatmap may limit the number of visible rows.
{% endhint %}

From the dropdown, select **Employees**, or switch to **Usage time** to break down engagement time instead of user count.

* Use the first **By** filter to group the results by organizational dimensions, such as **Division**, **Department**, or **Entity**, to identify affected business areas. The available options for grouping users are determined by the **user organization fields** you configured in your Nexthink environment.
* Use the second **By** filter to narrow the results further, across:
  * The application **Features**, which are determined by the application **Key pages** configured in Nexthink
  * Or, the device location (such as **Countries**, **Cities**, **States**, or **Sites**) to identify where adoption is weakest.

Visually identify group patterns with consistently high or low adoption, and application features with limited usage.

{% hint style="info" %}
On heatmaps with more than 10,000 rows, the system displays an infobar indicating that not all rows are shown, so the resulting ranking may not reflect the complete dataset.
{% endhint %}

{% hint style="warning" %}
If **user organization fields** are not fully enriched, the system may use fallback sources such as **Entra ID** data (if configured), which can affect user distribution across groups.

Refer to [Configuring user organization](/user-guide/administration/system-configuration/data-management/environment/product-configuration.md) to ensure you correctly create and enrich user organization fields.
{% endhint %}

## Investigate application insights

Review and select an **Insights** entry to understand the context and affected groups from the **Application expert** right-side panel. The insights cover:

* Why the selected adoption pattern matters
* **What the data shows** based on factual behavior

Cross-reference the adoption analysis with the application **Health** tab to correlate possible performance issues. Refer to [Analyzing application health](/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/health.md).

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FReWcTuCKOJBtCn3qMR4N%2F2026.8_AppEx_11_Rf2Jn9.png?alt=media&#x26;token=abee48ac-3471-4159-9400-1e3d0f010c21" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The system displays the ✦ sparkles icon to indicate AI-generated content or insights. AI is evolving rapidly and delivering great insights, but it can still make mistakes. Nexthink recommends validating your results to ensure accuracy and support informed decision-making.

Refer to the [Nexthink Insights - AI Model Card](https://docs.nexthink.com/legal/global-ai-hub/nexthink-insights-ai-model-card) documentation for more information.
{% endhint %}


---

# 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.nexthink.com/user-guide/applications/monitoring-applications/monitoring-web-applications/ahead/adoption.md?ask=<question>&goal=<user_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.