> 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/creator-program/introduction-welcome-to-creator/step-6-view-your-campaigns-performance.md).

# Passaggio 6: visualizza le performance della tua campagna

Quando avrai completato tutti i passaggi per avviare e rendere operativa la tua campagna, potrai visualizzare varie metriche di performance nel seguente report:

* [Report panoramico di contenuti e campagne](/brand/it/what-would-you-like-to-learn-about/creator-program/creator-reports/content-and-campaign-overview-report.md)

Consulta [Panoramica dei report dei creator](/brand/it/what-would-you-like-to-learn-about/creator-program/creator-reports/creator-reports-overview.md) per ottenere una ripartizione di come vengono aggregate le metriche.

## Best practice per l’analisi delle performance della tua campagna <a href="#section-idm235017160746596" id="section-idm235017160746596"></a>

* Quando analizzi le performance, considera quale livello di creator ha ottenuto i risultati migliori, quali tipi di contenuti e piattaforme sono stati più efficaci e quali temi di contenuto si sono rivelati i più coinvolgenti.
* Analizza una variabile alla volta (messaggio, piattaforma social, formato dei contenuti, ecc.), quindi analizza le performance per segmenti di creator per scoprire cosa guida davvero i risultati. Usa queste informazioni per individuare ciò che funziona meglio e perfezionare le campagne future con precisione basata sui dati.


---

# 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/creator-program/introduction-welcome-to-creator/step-6-view-your-campaigns-performance.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.