> 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/platform-features/multi-program-reports/data-lab-custom-reports/schedule-a-custom-report.md).

# Programar un informe personalizado

Los siguientes pasos le guiarán para programar un informe personalizado para una fecha específica o intervalos regulares:

1. En el menú de navegación izquierdo, seleccione ![](https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage]** → **Informes → Más informes**.
2. Seleccione **Categoría** y filtrar por **Integrado** ![](https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b5e1740618ed6571d97b8fed7c25a7678f85d375%2F299632fb6f4f91fbf9847471754cc6180e4284a65b4960af4c4ea472a159f552.svg?alt=media) **\[Casilla sin marcar]**.
3. Pase el cursor sobre el *Personalizado* informe que desea programar y seleccione **Ver**.
4. En la esquina superior derecha, selecciona ![](https://3147719151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-20b2988bdc1f8a97da2944a414cd37208d6827a3%2Fb90978d4ad1499f25650dc65b2602f870a0db03c6b9b1a5b49af856b768d2cbe.svg?alt=media) **\[Programar]**.
5. Establezca con qué frecuencia debe enviarse el informe usando la *Frecuencia* sección.
   * Los informes personalizados pueden enviarse **Diariamente, semanalmente**, o **Mensual**.
6. Seleccione qué **Formato** en el que se debe enviar el informe.
   * Los informes personalizados pueden enviarse como PDF, CSV *con* Metadatos o CSV *sin* Metadatos.

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Nota:</strong> Al optar por programar un CSV sin metadatos, el archivo ZIP descargado no tendrá el <code>metadata.json</code> archivo incluido.</p></div>
7. Elija si el informe debe entregarse mediante **Correo electrónico** o **FTP de socio**.
   * Especifique si impact.com aún debe **Enviar si el informe no tiene datos**.
8. Introduzca la información solicitada para el método de entrega que seleccionó en el Paso 5.
   * Obtenga más información sobre los tipos de entrega en la sección de referencia del método de entrega de la [Informes programados](/partner/es/sobre-que-te-gustaria-aprender/platform-features/reporting-for-partners/report-management/schedule-a-report-as-a-partner.md) artículo.
9. Seleccione **Programar**.


---

# 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/platform-features/multi-program-reports/data-lab-custom-reports/schedule-a-custom-report.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.