> 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/zh/ni-xiang-liao-jie-shen-me/seller-partnerships/amazon-seller-partnerships/amazon-seller-reporting-for-partners/seller-performance-by-product-for-partners.md).
# 卖家 - 面向合作伙伴的按商品绩效
该 *卖家 - 按产品划分的表现* 该报告显示您为 Amazon 上每个品牌产品带来了多少流量和收入。
## 管理报告
1. 在顶部导航栏中，选择 **报表 →** **更多报告**.
* 或者，在顶部导航栏中，选择 **报告** **→ 更多 → 更多报表**.
2. 从 *类别* 在搜索栏旁边的“类别”筛选器中，选择 **表现** 筛选器。
3. 选择 [**卖家 - 按产品划分的表现**](https://app.impact.com/secure/mediapartner/report/viewReport.report?handle=partner_seller_Perf_by_product).
* 您还可以将报告固定到顶部导航栏，只需将鼠标悬停在该行上并选择 **固定**.
4. 在报告标题下方，筛选您要查看的数据。设置好所需筛选条件后，选择  **\[搜索]**.
* 使用页面右上角的图标来  **\[计划]**,  **\[下载]** 以 PDF、Excel 或 CSV 格式下载报告，或者  **\[导出]** 通过 API 导出。
* 请参阅以下参考信息，以更好地理解该报告。
筛选条件参考
筛选器
说明
日期范围
按创建时间筛选数据。
产品类别
通过选择产品所属的类别来限制显示的产品，例如 鞋类.
报告数据列参考
| 列 | 亚马逊属性 | 说明 |
| ---------- | ------------------------------------ | ------------------------------------------------------ |
| 产品名称 | `productName` | 品牌产品目录中列出的产品名称。 |
| 品牌 | `AdGroupID` | 销售该产品的品牌名称。 |
| 点击量（DPV） | `attributedDetailPageViewsClicks14d` | 点击量 *详情页浏览量（DPV）* 指因广告点击将顾客引导至品牌产品详情页而计入您名下的次数。 |
| 加购点击量（ATC） | `attributedAddToCartClicks14d` | 因广告点击将顾客引导把品牌产品加入购物车而计入您名下的次数。 |
| 购买 | `AttributedPurchases` | 客户完成包含至少 1 件该品牌产品的购买的次数。购买包括产品租赁和订阅。 |
| 售出件数 | `unitsSold14d` | 客户在接触您的广告后于 Amazon 上购买的品牌产品总数量。可能会有多个 *售出件数* 在单个 *购买*. |
| 商品销售额 | `attributedSales14d` | 通过广告点击促成该计划中的产品购买所产生的总销售额。 |
---
# 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/zh/ni-xiang-liao-jie-shen-me/seller-partnerships/amazon-seller-partnerships/amazon-seller-reporting-for-partners/seller-performance-by-product-for-partners.md?ask=&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.