> 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/fr/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.md).

# Étape 3 : gérez les expériences de vos participants Advocate

L’étape suivante consisterait à personnaliser votre ambassadeur [l’expérience des participants](/brand/fr/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md). Vous pouvez envoyer des e-mails transactionnels à vos ambassadeurs clients et à toute personne qu’ils recommandent. Votre programme est initialement configuré avec des versions par défaut des e-mails du programme, mais nous vous recommandons [de personnaliser les e-mails de votre programme](/brand/fr/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) afin de garantir que les informations sont pertinentes pour votre programme et votre produit et d’offrir une impression plus personnalisée.

Ensuite vient la personnalisation de votre [widgets du programme](/brand/fr/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md) ou [microsites](/brand/fr/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences.md). Un widget de programme ou un microsite est le principal moyen pour vos participants d’accéder à votre programme de parrainage et de l’utiliser. Les widgets et les microsites renforcent l’image de marque du message de votre programme de parrainage et offrent à vos ambassadeurs clients un point de départ pour faire des recommandations.


---

# 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/fr/what-would-you-like-to-learn-about/advocate-program/introduction-welcome-to-advocate/step-3-manage-your-advocate-participant-experiences.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.