> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-7-utilize-reporting.md).

# ステップ7：レポートを活用する

[Advocate ではさまざまなレポートを提供しています](/brand/ja/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-program-reports-explained.md) プログラムと参加者データに関するもので、どの参加者や報酬が最も良い成果を上げているかを把握できます。これらのレポートを活用して、Advocate に最適な設定を見つけ、プログラムから最大限の価値を引き出せます。

また、次の機能も活用できます [紹介フィード](/brand/ja/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/view-and-manage-your-referrals-feed.md) 紹介を開始した人、Advocate のリンクがどこでクリックされたかなど、さらに詳しい洞察を得ることもできます。このようなデータは、紹介プログラムの最適な目標とアクションを設定する際に、より的確な判断を下すのに役立ちます。

分析スイートは、次の項目で構成されています [分析概要](/brand/ja/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) すべての Advocate プログラム全体のパフォーマンスを表示し、 [プログラム分析ページ](/brand/ja/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) では、個々の Advocate プログラムごとの詳細なパフォーマンス履歴を表示します。


---

# 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://help.impact.com/brand/ja/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-7-utilize-reporting.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.