> 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/advocate-rewards/referral-promo-codes-for-participants/set-up-referral-promo-codes.md).
# 设置推荐促销码
在你的项目规则中上传一批推荐促销码，然后通过你的小部件或微站点将它们提供给你的推荐人。
1. 在左侧导航菜单中，选择  **\[Engage] → 项目规则**.
2. 滚动到 *促销码* 部分，然后选择 **设置促销码**。对于推荐促销码，这可以设置为以下任一项： **可重复使用** 或 **一次性使用**.
* 建议使用一次性使用代码而不是可重复使用代码，因为这样有助于减少欺诈。
3. 选择你希望每位推荐人可获得的代码数量。只有在你选择创建 **一次性使用** 促销码。
* 这是推荐人一次持有的未使用代码数量，而不是终身上限。了解未使用代码 [如何替换已使用的代码](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/replace-used-promo-codes.md).
4. 你可以设置在促销码即将用完时希望收到通知的时间。
* 一旦代码数量达到你在通知部分设置的数量，就会向你发送一封电子邮件，提醒你代码所剩不多。务必确保你的项目不会降至零，因为只有在仍有未使用代码可用时，才能替换已使用的代码。请务必在代码不足时上传更多代码，以保持你的项目顺利运行。
5. 选择 **上传代码** 以上传一批推荐促销码。
* 你将被重定向到一个页面，在那里你可以以任一受支持的文件格式上传这批代码。
6. 选择 **保存** ，在你配置好促销码之后。系统会弹出一个窗口，询问你是否确定要保存。一旦启用一次性代码，此操作无法撤销。
7. 选择  **\[复选框]** 以自动将新的促销码模板应用到你的小部件。
* 或者，如果你已经有现有的小部件或微站点，也可以手动添加推荐促销码组件。你可以通过导航到 **内容** ，然后编辑你的小部件或微站点。在右侧选择 **添加** ，以向你现有的小部件或微站点添加一个组件。了解更多关于 [小部件和微站点组件](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/widget-and-microsite-components-explained.md).
一旦你上传了推荐促销码，这些代码将自动生成，并通过你已设置的 [小部件](/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/introduction-to-participant-experiences.md#widgets-0-0) 或微站点提供。
在下图中，推荐人获得了 5 个不同的代码，他们可以轮流切换并复制后分享给被推荐者。如果某个代码之前已被复制，你会在代码字段下方收到通知。这有助于避免你将同一个代码发送给多个人的情况。
---
# 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/advocate-rewards/referral-promo-codes-for-participants/set-up-referral-promo-codes.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.
