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

# Étape 4 : analyses du programme

Avec Amazon Seller, vous pouvez accéder à la gamme standard de rapports de performance d’impact.com, en plus des rapports spécifiques à Amazon Seller. Contrairement aux rapports de performance qui contiennent des métriques et des informations agrégées, vos [rapports](/brand/fr/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/amazon-seller-reporting-explained-for-brands.md) contiennent des données brutes directement d’Amazon :

* Utilisez le [Seller - Performance by Partner](/brand/fr/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-partner-for-brands.md) rapport pour identifier vos meilleurs performeurs et avoir une idée de ce qui fonctionne le mieux pour votre programme.
* Utilisez le [Seller - Performance by Product](/brand/fr/what-would-you-like-to-learn-about/seller-program/amazon-seller-program/amazon-seller-reporting-for-brands/seller-performance-by-product-for-brands.md) rapport pour analyser les performances des produits et avoir une idée du taux de conversion de chaque produit.

Vous pouvez [planifier des rapports](/brand/fr/what-would-you-like-to-learn-about/platform-features/multi-program-reports/report-management/schedule-reports.md) pour les envoyer automatiquement aux membres de l’équipe à intervalles réguliers.


---

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