> For the complete documentation index, see [llms.txt](https://docs-adopt.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-adopt.nexthink.com/core-analytics/core-analytics-key-concepts/targeting-dashboard.md).

# Targeting Dashboard

The Targeting Overview Dashboard allows you to see how content is performing across the targeted pages in your Adopt supported application.

**What it shows:** This shows the Number of Users that have accessed each System Page in the selected time period, what % of them have been Targeted and what % of those who were Targeted have Used Adopt

**How it’s used:** This data can be used to understand how the current targeting across an application is configured and at a detail level, which profiles are most likely to be interacting with Interventions on the page

**Common Question:** Why I am seeing only 29% of users Targeted on the ‘Time Off Balance’ Page (in the example here). By selecting on that row (or applying a Filter on the top of the page). You will see the Targeting Insights highlight which User Populations have been targeted. In this example Managers have been Targeted but not HR / Employees

## System Pages

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

**What it shows:** This shows the Number of Users that have accessed each System Page in the selected time period, what % of them have been Targeted and what % of those who were Targeted have Used Adopt​.

**How it’s used:** This data can be used to understand how the current targeting across an application is configured and at a detail level, which profiles are most likely to be interacting with Interventions on the page​.

**Common Question:** Why I am seeing only 29% of users Targeted on the ‘Time Off Balance’ Page (in the example here). By selecting on that row (or applying a Filter on the top of the page). You will see the Targeting Insights highlight which User Populations have been targeted. In this example Managers have been Targeted but not HR / Employees​.

## Targeting Insights

#### Profiling View

* This view shows you how Targeting and Adopt Usage varies by User Profile - you can use the filtering on the right hand side to switch between profiles
* This view can be helpful for determining if certain User Profiles aren’t being targeted on a page and also understand the dynamic of which users are most likely to be accessing the selected page

**Adopt Support View**

* This view highlights all of the Interventions that have been viewed whilst users were on the selected System Page

***Note:** Through Split Screen, Users may have searched for, and viewed, Interventions (PDF/Video) that weren’t directly targeted to the system page*

**Targeting Detail**

* This view will show you which Interventions are currently targeted at the selected System Page
* It is particularly useful to quickly assess targeting configuration across all Adopt Modules


---

# 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, and the optional `goal` query parameter:

```
GET https://docs-adopt.nexthink.com/core-analytics/core-analytics-key-concepts/targeting-dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
