> 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/platform/ja/user-guide/adopt/guide-insights-and-analytics.md).

# ガイドの洞察と採用分析

ウェブアプリケーションの導入状況と、そのインアプリガイドの使用状況をモニタリングするためには、

* **デジタル導入インサイト**ダッシュボードを使用して、[Web アプリケーションの導入を分析](/platform/ja/user-guide/adopt/guide-insights-and-analytics/analyzing-the-adoption-of-web-applications.md)します。
* インアプリガイドが導入されたアプリケーションに対しては、
  * アプリケーション固有のダッシュボードの **ガイド** タブから、[ガイド](/platform/ja/user-guide/adopt/guide-insights-and-analytics/understanding-the-adoption-tab.md)の使用状況を監視します。
  * **ガイド** タブで特定のガイド名をクリックすると、[そのガイドの個別の使用状況を追跡](/platform/ja/user-guide/adopt/guide-insights-and-analytics/tracking-specific-guide-usage.md)できます。

NQL Guides テーブルのクエリについては、[ガイドの高度なユースケース](/platform/ja/user-guide/adopt/adopt-advanced-use-cases.md#guides-specific-nql-tables)に関するドキュメントを参照してください。

{% hint style="info" %}
より大きな効果を得るには、ガイドの追跡にとどまらず、[デジタル導入戦略を実行](/platform/ja/solutions/executing-a-digital-adoption-strategy.md)してください。これにより、Guides ツールと Nexthink Infinity の強力な DEX 分析を組み合わせることができます。
{% endhint %}

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-f58324d8a37273f32878ed831c875b9d793a80ae%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/platform/ja/user-guide/adopt/guide-insights-and-analytics.md?ask=<question>&goal=<user_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.
