> 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/what-would-you-like-to-learn-about/seller-partnerships/amazon-seller-partnerships/amazon-seller-reporting-for-partners/seller-performance-by-product-for-partners.md).
# Seller - Performance by Product for Partners
The *Seller - Performance by Product* report shows you how much traffic and revenue you're generating for each brand product on Amazon.
## Manage the report
1. From the top navigation bar, select **Reports →** **More Reports**.
* Alternatively, from the top navigation bar, select **Reports** **→ More → More Reports**.
2. From the *Category* filter next to the search bar, select the **Performance** filter.
3. Select [**Seller - Performance by Product**](https://app.impact.com/secure/mediapartner/report/viewReport.report?handle=partner_seller_Perf_by_product).
* You can also pin the report to your top navigation bar by hovering over the row and selecting **Pin**.
4. Below the report heading, filter for the data you want to view. Once you've set the filters you want, select  **\[Search]**.
* Use the icons at the top-right of the page to  **\[Schedule]**,  **\[Download]** the report in PDF, Excel, or CSV format, or  **\[Export]** it via API.
* See the references below to better understand the report.
Filter reference
Filter
Description
Date Range
Filter data by when it was created.
Product category
Limit which products you see by selecting the category they fall under, e.g., Shoes.
Report data column reference
| Column | Amazon Attribute | Description |
| ------------------------ | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Product Name | `productName` | The name of the product as listed in the brand's product catalog. |
| Brand | `AdGroupID` | The name of the brand who sells the product. |
| Clicks (DPV) | `attributedDetailPageViewsClicks14d` | Clicks *Detail Page Views (DPV)* refers to the number of times you were credited for driving customers to the brand's product detail pages through ad clicks. |
| Add to Cart Clicks (ATC) | `attributedAddToCartClicks14d` | The number of times you were credited for driving customers to add the brand's products to their carts through ad clicks. |
| Purchases | `AttributedPurchases` | The number of times a customer made a purchase that included at least 1 of the brand's products. Purchases include product rentals and subscriptions. |
| Units Sold | `unitsSold14d` | The total quantity of brand products that customers purchased on Amazon after exposure to your ad. There could be multiple *Units Sold* in a single *Purchase*. |
| Product Sales | `attributedSales14d` | The total sales amount that resulted from you driving product purchases for the program through ad clicks. |
---
# 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/what-would-you-like-to-learn-about/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.