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. 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.

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.

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.

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.

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.

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.

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.

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 to ensure you correctly create and enrich user organization fields.

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.

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 documentation for more information.