> 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/view-referral-promo-codes.md).

# 查看推荐促销码

你可以在 *查看代码* 页面中查看多项详细信息。通过查看代码类型，可以区分一次性代码和多次使用代码。你还可以查看哪些代码已被使用，以及哪些推荐对应了哪些推广者。

{% hint style="success" %}
**注意**：一次性代码是尽量降低促销代码被欺诈使用风险的好方法。多次使用代码通常会在第三方网站上分享，而一次性代码只能使用一次，因此不太可能在不可靠的来源中传播。
{% endhint %}

1. 在左侧导航菜单中，选择 ![](https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] →** **奖励 → 代码管理器**.
2. 选择要查看代码的参与者。
3. 在 *查看代码* 页面中，你可以找到所有相关信息，包括已发放的代码类型、已使用的代码等。

<div data-with-frame="true"><figure><img src="https://4048883401-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F5G6QGfUR6MiONqv2ki1N%2FScreenshot%202026-05-19%20at%2012.12.21.png?alt=media&#x26;token=e2c4241a-5bb5-430e-8c42-cde9a31f2938" alt=""><figcaption></figcaption></figure></div>


---

# 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/view-referral-promo-codes.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.
