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

# Passaggio 7: utilizza i report

[Advocate offre report diversi](/brand/it/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-program-reports-explained.md) per i dati del tuo programma e dei partecipanti che ti consente di tenere traccia di quali partecipanti e ricompense stanno offrendo i migliori risultati. Questi report possono essere utilizzati per sfruttare le impostazioni migliori per i tuoi promotori, per assicurarti di ottenere il massimo valore dai tuoi programmi.

Puoi anche utilizzare il [feed dei referral](/brand/it/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/view-and-manage-your-referrals-feed.md) per ulteriori approfondimenti, ad esempio su chi ha avviato i referral, dove è stato cliccato il link dell'advocate e altro ancora. Questi dati ti aiutano a prendere decisioni più informate quando imposti gli obiettivi e le azioni migliori per il tuo programma di referral.

La suite di analisi è composta da un [panoramica delle analisi](/brand/it/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) che mostra le prestazioni di tutti i tuoi programmi advocate e la [pagina di analisi del programma](/brand/it/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) mostrerà una cronologia dettagliata delle prestazioni per ciascun singolo programma advocate.


---

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