> 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/zh/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，除了可查看 impact.com 的标准绩效报表外，您还可以访问 Amazon Seller 特有的报表。与包含汇总指标和洞察的绩效报表不同，您的 [报表](/brand/zh/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 的原始数据：

* 使用 [卖家 - 按合作伙伴划分的绩效](/brand/zh/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-partner-for-brands.md) 报表，以识别表现最佳的合作伙伴，并了解最适合您的计划的做法。
* 使用 [卖家 - 按产品划分的绩效](/brand/zh/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-product-for-brands.md) 报表，以分析产品表现并了解各产品的转化率。

您可以 [安排报表定时发送](/brand/zh/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/zh/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.