> 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.md).

# 参与者推荐促销码说明

{% hint style="danger" %}
**重要**：一旦该功能在您的计划中开启，就无法关闭。
{% endhint %}

推荐促销代码是将归因和奖励压缩为 1 个步骤的绝佳方式，位于 **开始** 推荐流程的起始处。优惠券由客户倡导者提供给被推荐的朋友，并提供折扣。一旦被推荐的朋友在结账时使用其促销代码，该代码就会归因到客户倡导者，后者随后获得奖励。

您可以通过在计划规则中上传促销代码，为您的倡导者创建推荐促销代码。一旦您设置好 [计划规则](/brand/zh/what-would-you-like-to-learn-about/advocate-program/getting-started-with-advocate/configure-your-advocate-program.md) ，请导航到 *促销代码* 部分以上传一批推荐促销代码。

{% hint style="success" %}
**注意**：此功能与 [燃油箱奖励](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/fuel-tank-rewards-explained.md)不同。燃油箱奖励也使用代码，但这些代码仅用于奖励参与者——不会在倡导者和被推荐的朋友之间创建归因关系。
{% endhint %}

了解如何：

* [设置推荐促销代码](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/set-up-referral-promo-codes.md)
* [替换已使用的促销代码](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/replace-used-promo-codes.md)
* [查看推荐促销代码](/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/referral-promo-codes-for-participants/view-referral-promo-codes.md)

## 事件时间归因

推荐通过用户 upsert 进行归因，这些操作会通过 API 调用、用户导入，甚至小组件加载来发生。推荐促销代码也可以随购买事件一并回传给我们。您可以在 `OrderPromoCode` 中通过转化 API 将事件传递给我们。了解如何创建 [转化事件](https://integrations.impact.com/brand-api-reference/reference/conversions).


---

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