> 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/fuel-tank-rewards-explained.md).

# 燃料罐奖励说明

**有限**：礼品卡奖励仅适用于某些计划版本。 [联系支持团队](https://app.impact.com/support/portal.ihtml?createTicket=true&) 以升级您的推荐计划并获取访问权限。

燃料箱功能可通过专属优惠码简化奖励发放流程。您的推荐者可以兑换这些代码以获得奖励，包括折扣、积分和其他奖励类型。

您可以通过 impact.com 账户添加、删除或管理优惠码，详情请参阅 [设置燃料箱奖励](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/set-up-a-fuel-tank-reward.md) 了解相关指南。您还可以跟踪每个优惠码发给了哪位推荐者，并在需要时取消其奖励。

燃料箱的优惠码由您提供。您可以自行创建这些代码，也可以使用现有的电商或计费平台来生成。许多主流电商和计费平台（包括 Shopify、WooCommerce、Magento、BigCommerce 和 Recurly）都支持批量生成代码并导出。

在电商平台中生成代码时，您还可以定义其使用规则。例如，您可以决定：

* 每个代码的面值
* 代码适用的产品或服务
* 使用代码前所需的最低消费金额

{% hint style="info" %}
**注意：** 代码的运作方式由创建该代码的电商或计费平台控制，而非您的推荐计划。如果您使用 Shopify，还可以通过我们的 [设置同步代码](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/advocate-rewards/set-up-a-fuel-tank-reward.md#synced-codes-for-shopify-0-3) 进行配置： [Shopify 集成](https://integrations.impact.com/integration-guides/for-brands/plugin-integrations/e-commerce/integrate-with-shopify).
{% endhint %}

燃料箱奖励可以集成到 [即时访问组件](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/widget-experiences/set-up-an-instant-access-widget.md), [验证访问组件](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/widget-experiences/widget-types-explained.md)和 [微型网站](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/set-up-a-microsite.md).

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-6039e292ddcb386f437a9ba7b5154f17a268711e%2F297c5f9d05d69f751546306aedadebf3e1665e02ab59b5e9446c3e06698475c0.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### 参与者体验

优惠码可以集成到计划组件或微型网站中，用于奖励推荐者及其推荐的好友。

推荐者通常会在其推荐对象完成转化后获得奖励。转化成功后，系统会自动通过电子邮件通知推荐者。随后，推荐者会收到一个专属优惠码，可用该码兑换奖励。

对于受推荐的好友，理想的体验是在点击推荐者的分享链接后立即收到折扣码，以便在首次结账时使用。您可以在计划落地页上设置好友组件来实现这一点。

{% hint style="info" %}
**流程示例：** 推荐者分享链接 → 好友打开链接并进入您的落地页 → 好友组件弹出（或嵌入页面）→ 好友提供电子邮箱地址 → 好友看到折扣码。
{% endhint %}

如果好友没有立即购买，也可以通过电子邮件向其发送折扣码。


---

# 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/fuel-tank-rewards-explained.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.
