> 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/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/introduction-welcome-to-impact.com/step-4-program-insights.md).

# Fase 4: approfondimenti sul programma

Con Amazon Seller, puoi accedere alla gamma standard di report sulle prestazioni di impact.com, oltre ai report specifici di Amazon Seller. A differenza dei report sulle prestazioni che contengono metriche e approfondimenti aggregati, i tuoi [report](/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/amazon-seller-reporting-explained-for-brands.md) contengono dati grezzi direttamente da Amazon:

* Usa il [Seller - Performance by Partner](/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-partner-for-brands.md) report per identificare i tuoi migliori performer e farti un'idea di ciò che funziona meglio per il tuo programma.
* Usa il [Seller - Performance by Product](/brand/it/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-product-for-brands.md) report per analizzare le prestazioni dei prodotti e farti un'idea del tasso di conversione di ciascun prodotto.

Puoi [programmare i report](/brand/it/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/schedule-reports.md) per inviarli automaticamente ai membri del team a intervalli regolari.


---

# 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/it/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.