> 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/es/what-would-you-like-to-learn-about/creator-program/introduction-welcome-to-creator/step-6-view-your-campaigns-performance.md).

# Paso 6: Consulta el rendimiento de tu campaña

Cuando hayas completado todos los pasos para poner en marcha tu campaña, podrás ver diversas métricas de rendimiento en el siguiente informe:

* [Informe general de contenido y campaña](/brand/es/what-would-you-like-to-learn-about/creator-program/creator-reports/content-and-campaign-overview-report.md)

Consulta [Resumen de informes para creadores](/brand/es/what-would-you-like-to-learn-about/creator-program/creator-reports/creator-reports-overview.md) para obtener un desglose de cómo se agregan las métricas.

## Buenas prácticas al revisar el rendimiento de tu campaña <a href="#section-idm235017160746596" id="section-idm235017160746596"></a>

* Al analizar el rendimiento, considera qué nivel de creadores tuvo el mejor desempeño, qué tipos de contenido y plataformas fueron los más eficaces y qué temas de contenido resultaron más atractivos.
* Analiza una variable (mensajería, red social, formato de contenido, etc.) a la vez y luego analiza el rendimiento por segmentos de creadores para descubrir qué impulsa realmente los resultados. Usa estos aprendizajes para identificar qué funciona mejor y perfeccionar futuras campañas con precisión basada en datos.


---

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