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

# 第 3 步：管理你的 advocate 参与者体验

下一步是自定义你的客户倡导者 [参与者体验](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md)。您可以向您的客户倡导者以及他们推荐的任何人发送交易性电子邮件。您的项目最初已配置为使用项目邮件的默认版本，但我们建议 [定制您的项目邮件](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-experiences/create-and-customize-advocate-program-emails.md) 以确保信息与您的项目和产品相关，并营造更个性化的感觉。

接下来是自定义您的 [项目小组件](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md) 或 [微型网站](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences.md)。项目小组件或微型网站是参与者访问和使用您的推荐计划的主要方式。小组件和微型网站是对您的推荐计划信息的品牌化强化，并为您的客户倡导者提供开始进行推荐的起点。


---

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