> 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/manage-advocate-participant-experiences/introduction-to-participant-experiences.md).
# 参与者体验简介
参加 PXA 课程
您的推荐者及其推荐的朋友可以通过该计划的 widget、微站及其事务性电子邮件与您的 Advocate 计划互动。这些元素构成了您的推荐者及其朋友的 *参与者体验* 推荐计划的一部分。
您可以从 *内容* 您在 impact.com 账户中的页面调整各触点的品牌标识、内容、文案和组件。本指南提供每个触点的概览，并附有更详细文档的链接。
#### 小组件
小组件是推荐计划中的品牌触点，可强化推荐计划的文案，并为您的推荐者提供发起推荐的起点。它们为推荐者提供一个空间，用于获取和分享其推荐链接和代码、查看推荐历史记录，并访问诸如 [奖励兑换](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/reward-exchange-explained.md).
小组件可以是以下任一种： *已验证访问*，可提供应用内体验；或者 *即时访问*，这通常用于电商推荐计划结账流程的一部分。
您的推荐计划可能包含多个小组件，或由小组件与微站组合而成。
了解更多关于 [小组件体验](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences.md).
#### 事务性电子邮件
计划邮件会在参与者推荐旅程中的关键节点发送给他们，例如推荐已启动时，或者他们获得奖励时。您可以在设置计划规则时确定哪些操作会触发计划邮件。
{% hint style="info" %}
**注意：** impact.com 不支持通过平台发送营销电子邮件，因此您需要通过单独的服务或集成来推广您的推荐计划。
{% endhint %}
了解更多关于 [电子邮件体验](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/email-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/manage-advocate-participant-experiences/introduction-to-participant-experiences.md?ask=&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.
