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

# Passaggio 1: configura le integrazioni e il tracciamento dell'attribuzione dei referral

Ti sarà stato fornito un separato *Piano di implementazione tecnica* personalizzato in base ai requisiti e alle esigenze specifiche della tua implementazione. Una volta completata l'implementazione tecnica, puoi procedere con la configurazione del programma.

Il tuo [tracciamento dell'attribuzione dei referral](https://integrations.impact.com/integration-guides/for-brands/advocate/advocate-tracking-integrations/advocate-installation-scripts) è ciò che ti aiuta a tenere traccia di chi effettua la segnalazione, da dove proviene la segnalazione e quante segnalazioni sono state effettuate.

Quando crei un programma Advocate, puoi condividere con esso i tipi di evento del tuo programma. Questo ti consente di sfruttare le integrazioni impact.com esistenti e di condividere tra esse i dati di conversione. Gli stessi dati possono configurare le regole del tuo programma 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/it/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.