New DEX certifications launch at Experience '26. Get certified and learn from experts in your field.
Register now
Ctrlk
LearnDocumentationSupportCommunity
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Configuring AHEAD

Configure the required settings to enable the AHEAD dashboards and ensure data appears correctly across the Adoption, Health, Efficiency, Affordability, and Delight tabs.

AHEAD applies to web and hybrid (web and desktop) applications only.

Configure user organization fields

Configure user organization fields to classify employees by department or business unit and enable organizational breakdowns in the dashboards.

  • Define up to six levels of organizational hierarchy (for example, Business Unit, Department, Region) to enable breakdowns in the dashboards. Refer to Configuring user organization for more information.

  • If user organization data is missing, configure the Entra ID connector to map dashboard data to your organization structure. Refer to Connector for Microsoft Entra ID (Azure AD) for more information.

Enable the AHEAD view

The AHEAD view is enabled by default for each web application. To turn it off or back on, use the Enable AHEAD view toggle on the web application's Application settings > Web configuration > AHEAD tab.

Refer to Configuring web applications for more information.

Refer to AHEAD dashboard enablement for more information on enabling AHEAD.

Configure Adoption settings

Enable web-usage time collection for the target application to capture usage duration data and populate the Adoption tab.

Select Managing applications to go to Manage Applications > Settings, and verify that Web usage time monitoring is enabled.

Configure Health settings

The Health tab compares application performance against the global Nexthink benchmark by default.

Select Setting application thresholds to go to the web application's Application settings > Web configuration > Thresholds tab, and set application thresholds as a fallback to categorize performance when benchmark data is unavailable for this application.

The Health heatmap can break down data by application feature, based on the Key pages configured for the application. Refer to Configuring Key pages to set them up.

Configure Efficiency settings

Select ServiceNow Tickets connector to go to Administration > Inbound connectors > New connector, and configure the ServiceNow Tickets connector to bring ticket data into Nexthink and enable the Efficiency tab.

The ServiceNow Tickets connector can collect both incidents and service requests. The Efficiency tab counts only service requests.

The Efficiency tab requires the Tickets data model to be visible for the user's role. Refer to Data model visibility for more information.

Configure Affordability settings

Configure software metering thresholds for active license usage and total license counts to calculate the percentage of licenses in use in the Affordability tab.

  • Select Managing Software Metering to go to Software Metering > Manage software metering, and configure software metering thresholds to set the minimum usage that counts as an active license.

  • Select Setting application licenses to go to the web application's Application settings > Web configuration > Licenses tab, and enter the total number of licenses available for the application to calculate the license utilization rate shown in the Affordability tab.

When multiple applications share the same software metering entry (for example, Salesforce Lightning and Salesforce Classic under Salesforce), the same threshold applies to each one.

Nexthink enables Affordability by default. If an application has no software metering configured, select Enable now on the tab to configure it automatically, using an AI-suggested usage threshold. Review or adjust the threshold from the Manage software metering page.

Configure Delight settings

Enable the Collect feedback toggle on the web application's settings to collect employee satisfaction ratings and populate the Delight tab.

The Delight score also uses frustrating page loads as a data source, which requires no additional configuration. If the survey is not configured for an application, the Delight score is calculated using frustrating page loads alone.

Nexthink limits how often the system surveys the same employee:

  • 30 days between surveys for different applications, regardless of whether the employee responded

  • 90 days between surveys for the same application if the employee declined or answered partially

  • 90 days between surveys for the same application if the employee answered fully

RELATED TASKS

Last updated

Was this helpful?