> 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/deriving-insights/targeting-dashboard.md).

# Targeting Dashboard

<figure><img src="/files/04ku8PJHTxiVOeQCfnlZ" alt=""><figcaption></figcaption></figure>

A. The Targeting dashboard, found in the navigation pane on the left, is where you can drill into the insights that you’ve discovered. See the detailed breakdown of data, such as specific system pages/processes and how users are spending time there. Using this information, you can create a plan to target the most at need users.

B. Within the Targeting dashboard, you can navigate to the Adopt Support View tab to see what support is available and what is being utilized. If it appears that users are not utilizing the support content effectively, it may be necessary to remind them that Adopt exists. Alternatively, if they are engaged with support content, it may be that more is needed, or tweaks to the content may be required.


---

# 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/deriving-insights/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.
