> 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/adopt/guide-insights-and-analytics.md).
# Guide insights and adoption analytics
Monitor the adoption of web applications and the usage of their deployed in-app guides by:
* [Analyzing the adoption of web applications](/user-guide/adopt/guide-insights-and-analytics/analyzing-the-adoption-of-web-applications.md) using the **Digital adoption insights** dashboard.
* For applications with deployed in-app guides:
* [Monitoring guides](/user-guide/adopt/guide-insights-and-analytics/understanding-the-adoption-tab.md) usage from the **Guides** tab under the application-specific dashboard.
* Click a specific guide's name in the **Guides** tab to [track that guide's individual usage](/user-guide/adopt/guide-insights-and-analytics/tracking-specific-guide-usage.md).
Refer to the [Guides advanced use cases](/user-guide/adopt/adopt-advanced-use-cases.md#guides-specific-nql-tables) documentation to learn about querying NQL Guides tables.
{% hint style="info" %}
To drive greater impact, go beyond guide tracking by [Executing a digital adoption strategy](/solutions/executing-a-digital-adoption-strategy.md)—combining Guides tools and Nexthink Infinity powerful DEX analytics.
{% 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/adopt/guide-insights-and-analytics.md?ask=&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.
