> 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/advocate-program/introduction-welcome-to-advocate/step-7-utilize-reporting.md).

# Étape 7 : utilisez les rapports

[Advocate propose différents rapports](/brand/fr/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-program-reports-explained.md) pour les données de votre programme et de vos participants qui vous permettent de suivre quels participants et quelles récompenses offrent les meilleurs résultats. Ces rapports peuvent être utilisés pour tirer parti des meilleurs paramètres pour vos ambassadeurs afin de vous assurer de tirer un maximum de valeur de vos programmes.

Vous pouvez également utiliser le [flux des parrainages](/brand/fr/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/view-and-manage-your-referrals-feed.md) pour obtenir d'autres informations, telles que qui a initié les parrainages, où le lien de l'ambassadeur a été cliqué, et plus encore. Ces données vous aident à prendre de meilleures décisions éclairées lors de la définition des meilleurs objectifs et actions pour votre programme de parrainage.

La suite analytique comprend un [aperçu analytique](/brand/fr/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) qui affiche les performances de l'ensemble de vos programmes ambassadeurs et la [page d'analyse du programme](/brand/fr/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) affichera un historique détaillé des performances pour chaque programme ambassadeur individuel.


---

# 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/advocate-program/introduction-welcome-to-advocate/step-7-utilize-reporting.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.