> 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/redeem-rewards-in-bulk.md).

# 批量兑换奖励

奖励通常会通过你与 Advocate 的某个集成进行兑换。如果你需要在外部系统中手动发放奖励，那么可以使用此批量奖励兑换流程来更新参与者的可用奖励余额。

{% hint style="success" %}
**注意：** 此流程不会向参与者发放具体奖励——例如积分、礼品卡或优惠码。相反，它会更新你的记录，以便在你通过其他系统兑换奖励后，准确显示参与者的奖励余额。
{% endhint %}

{% stepper %}
{% step %}
**第 1 步：下载“按用户显示可用奖励余额”报告**

该报告列出了各个项目中所有具有可用奖励余额的参与者。你可以使用此报告在外部系统中手动发放奖励。

1. 从左侧导航菜单中，选择 ![](https://res.cloudinary.com/product-enablement/image/upload/v1768905009/Accessibility%20Icons/engage-v2.svg) **\[Engage] → 报告 → 导入与导出**.
2. 选择 **创建报告**.
3. 在……下 *选择报告类型*，选择 **按用户显示可用奖励余额**.
4. 你也可以选择特定的奖励单位，以缩小参与者列表范围。如果你想将生成的报告限制为通过外部服务支付的某一特定奖励单位，这会很有用。
5. 选择报告格式（.CSV 或 Excel）。
6. 选择 **创建报告**.

生成的报告链接将发送到与此账户关联的电子邮件地址。
{% endstep %}

{% step %}
**第 2 步：更新报告**

在你于外部系统中手动发放奖励后，需要更新 *按用户显示可用奖励余额* 报告。这样可让 Advocate 知道哪些参与者的奖励已被发放。

1. 使用电子表格应用程序，打开 *按用户显示可用奖励余额* 报告。
2. 对于你已手动发放奖励的每位参与者，更新 `valueToRedeem` 列。仅接受正数。
3. 将报告保存为 .CSV 格式。

**兑换说明**

* 奖励余额需要以相同单位（*例如*. `分` 或 `现金/USD`）进行兑换，且余额显示的单位也应为（*即* 不能按分的金额兑换美元）。
* 导入时只会处理对 `valueToRedeem` 字段的更改。
* 奖励余额中的单个奖励将按其到期时间顺序进行兑换（`dateExpires`），然后按它们向参与者开放的时间顺序进行兑换（`dateGiven`).
* 仅会兑换状态为 `AVAILABLE` 的奖励。
* 兑换时，小数单位的分数部分将被截断（*例如* 兑换“10.556 USD”时，只会兑换“10.55 USD”）。
  {% endstep %}

{% step %}
**第 3 步：上传更新后的报告**

最后，你需要将更新后的 *按用户显示可用奖励余额* 包含当前奖励余额的报告重新上传到 Advocate。

1. 从左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 报告 → 导入与导出**.
2. 选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-06e12321258e7eb7ac63ef7e73640b29fcf2baad%2Fcff634f1183ca82d3b56ab55dd636140372687d8dbc6520872cdbe5010347326.svg?alt=media) **导入**.
3. 在……下 *导入类型*，选择 **更新用户奖励余额**.
4. 要添加你更新后的报告，请选择 **选择文件**.
5. 选择 **导入**.

导入完成后，会发送一封确认电子邮件。根据队列和文件大小，导入最多可能需要 30 分钟。
{% endstep %}
{% endstepper %}


---

# 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/redeem-rewards-in-bulk.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.