> 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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-4-program-insights.md).

# ステップ4：プログラムのインサイト

Amazon Sellerでは、Amazon Seller専用のレポートに加えて、impact.comの標準的なパフォーマンスレポートも利用できます。集計された指標やインサイトを含むパフォーマンスレポートとは異なり、 [レポートには](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/amazon-seller-reporting-explained-for-brands.md) Amazonから直接取得した生データが含まれます。

* 「 [Seller - Performance by Partner](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-partner-for-brands.md) 」レポートを使用して、最も成果を上げているパートナーを特定し、プログラムで何が最も効果的かを把握できます。
* 「 [Seller - Performance by Product](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-product-for-brands.md) 」レポートを使用して、商品ごとのパフォーマンスを分析し、各商品のコンバージョン率を把握できます。

レポートを [スケジュール](https://help.impact.com/brand/ja/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/schedule-reports.md) 設定すると、チームメンバーに定期的に自動配信できます。


---

# 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/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-4-program-insights.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.
