> 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/de/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-7-utilize-reporting.md).

# Schritt 7: Reporting nutzen

[Advocate bietet verschiedene Berichte an](/brand/de/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-program-reports-explained.md) für Ihre Programm- und Teilnehmerdaten, mit denen Sie im Blick behalten können, welche Teilnehmer und Prämien die besten Ergebnisse liefern. Diese Berichte können verwendet werden, um die besten Einstellungen für Ihre Advocates zu nutzen und sicherzustellen, dass Sie den maximalen Nutzen aus Ihren Programmen ziehen.

Sie können auch die [Empfehlungs-Feed](/brand/de/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/view-and-manage-your-referrals-feed.md) für weitere Einblicke wie beispielsweise, wer Empfehlungen initiiert hat, wo auf den Link des Advocates geklickt wurde und mehr. Solche Daten helfen Ihnen dabei, besser informierte Entscheidungen zu treffen, wenn Sie die besten Ziele und Aktionen für Ihr Empfehlungsprogramm festlegen.

Die Analytics-Suite besteht aus einer [Analytics-Übersicht](/brand/de/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) die die Leistung über alle Ihre Advocate-Programme hinweg anzeigt und die [Programm-Analytics-Seite](/brand/de/what-would-you-like-to-learn-about/advocate-program/advocate-reporting-and-analytics/advocate-analytics-overview-explained.md) zeigt eine detaillierte Leistungshistorie für jedes einzelne Advocate-Programm an.


---

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