> 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/beta-product-boost/product-boost-campaign-management/bulk-upload-multiple-product-boost-payout-rules.md).

# 批量上传多个产品提升结算规则

当您 [上传 Product Boost 活动](/brand/zh/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/bulk-upload-product-boost-campaigns.md) 批量上传时，您可以向单个活动添加多个支付规则。您可以通过添加 *续行* *行* 在创建或修改期间，位于活动行之后。

## 在批量上传中包含多个支付规则

1. 当 [准备您的 CSV 或 Excel 文件时](/brand/zh/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/bulk-upload-product-boost-campaigns.md#prepare-your-file) 进行上传时，找到您希望添加额外支付规则的活动行。
2. 在其下方再添加一行。
3. 在续行中，留空 `活动名称` 留空。
   * 这使系统将您的续行识别为同一活动的额外支付规则，而不是另一条活动记录。
4. 请参见 [附加行指南](#additional-row-guidelines) 说明续行中应填写哪些列。
   * 下方截图显示文件上传在验证期间的呈现方式：

<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%2FBxnOSdEg66dsGFlPPq7j%2FScreenshot_2026-07-23_at_10_08_16%E2%80%AFAM.png?alt=media&amp;token=ad435b1f-2f91-4115-9e63-e56259e234c1" alt="Bulk upload validation view showing a campaign row and its continuation row."><figcaption></figcaption></figure></div>

<details>

<summary>附加行指南</summary>

向 Product Boost 活动添加多个支付规则时，请将这些指南应用于任何续行。

| 列名称     | 说明                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 活动名称    | 留空，以将此标记为附属于上方所定义活动的续行。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
| 事件类型 ID | <p>重复主行的事件类型 ID。</p><p>或者，要在同一活动中按另一事件类型发放，输入不同的 <code>事件类型 ID</code>.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| 支付类型    | 输入此附加规则的支付类型。（例如 `百分比` 或 `固定`).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| 支付值     | 输入此附加规则的支付金额。必须大于 0。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| 规则      | <ul><li>按以下格式输入 1 条资格条件 <code>\[变量 运算符 值]</code> （例如， <code>\[ITEM\_SKU 为 HYD-2000]</code>），或了解如何设置 <a href="/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/how-payout-rules-work.md">支付规则</a>.</li><li>每个续行只能输入 1 条支付规则。</li><li>请勾选 <a href="/brand/zh/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/bulk-upload-product-boost-campaigns.md#validation-error-reference">验证错误参考</a> 如果未通过验证。</li></ul> |

有关字段格式和允许值的完整列表，请参阅 [批量上传 Product Boost 活动](/brand/zh/what-would-you-like-to-learn-about/beta-product-boost/product-boost-campaign-management/bulk-upload-product-boost-campaigns.md).

</details>

### 带有续行的示例文件

{% code overflow="wrap" %}

```
活动名称,方法,活动 ID,供应商 ID,内部活动 ID,资金,资格类型,合作伙伴 ID,合作伙伴组 ID,预算,强制预算,草稿,开始日期,结束日期,事件类型 ID,支付类型,支付值,优先级,规则
冬季靴子促销,添加,,,EXAMPLE-001,,已加入合作伙伴,,,1000.00,否,是,2026-08-01T00:00:00-07:00,2026-08-31T23:59:59-07:00,17897,固定,5.00,10,[ITEM_SKU 为 BOOT123]
,,,,,,,,,,,,17897,固定,3.00,,[ITEM_SKU 为 BOOT456]
```

{% endcode %}

{% hint style="warning" %}
**修改时重要提示：** 在修改活动期间更新规则字段会清除并替换该活动中任何现有规则和事件类型。如果您想在保留现有事件类型或支付规则的同时添加续行，则需要将每一项都作为一个 [续行](#additional-row-guidelines).
{% 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/beta-product-boost/product-boost-campaign-management/bulk-upload-multiple-product-boost-payout-rules.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.