> 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/partner/ja/nitsuitebitaidesuka/getting-started/readme-1/im-a-partner/step-6-review-reporting-stats-and-grow.md).

# ステップ6：レポート統計を確認して成長しましょう！

ブランドからの報酬を獲得し始めたら、 [詳細アクション一覧レポート](https://help.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/reporting-for-partners/advanced-action-listing-report-for-partners.md) を使って、発生させたコンバージョンの詳細情報を確認しましょう。 [利用可能なレポート](https://help.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/reporting-for-partners/all-reports-available-to-partners.md) を使って、最も大きなメリットをもたらすブランドやプロモーションを特定しましょう。 [保留中](https://help.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/finance/payments-withdrawals-and-balance/your-balance/pending-screen-overview-for-partners.md) と [残高](https://help.impact.com/partner/ja/nitsuitebitaidesuka/platform-features/finance/payments-withdrawals-and-balance/your-balance/balance-screen-overview-for-partners.md) の画面で、利用可能な報酬と、まだ保留中の報酬を確認しましょう。

Discoveryやメールキャンペーンを通じて、厳選されたブランドや商品のコレクションを活用することもできます。これらのコレクションはimpact.comが厳選したもので、収益の拡大や報酬の増加に役立つおすすめのブランドや商品をご紹介しています。


---

# 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/partner/ja/nitsuitebitaidesuka/getting-started/readme-1/im-a-partner/step-6-review-reporting-stats-and-grow.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.
