> 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/advocate-program/introduction-welcome-to-advocate/step-1-set-up-your-integrations-and-referral-attribution-tracking.md).

# Paso 1: Configura tus integraciones y el seguimiento de atribución de referidos

Se le habrá proporcionado por separado *Plan de implementación técnica* personalizado según los requisitos y necesidades únicos de su implementación. Una vez completada la implementación técnica, puede continuar con la configuración del programa.

Tu [seguimiento de atribución de referencias](https://integrations.impact.com/integration-guides/for-brands/advocate/advocate-tracking-integrations/advocate-installation-scripts) es lo que le ayuda a hacer seguimiento de quién refiere, de dónde provino la referencia y cuántas referencias se hicieron.

Al crear un programa Advocate, puede compartir con él los tipos de eventos de su programa. Esto le permite aprovechar las integraciones existentes de impact.com y compartir datos de conversión entre ellas. Estos mismos datos pueden configurar las reglas de su programa 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/es/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-1-set-up-your-integrations-and-referral-attribution-tracking.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.