> 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/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.md).

# 创建付款组

<a href="https://pxa.impact.com/student/activity/1117596?sid=0c0e3e5c-54c9-4435-9bee-ebcdccb7f292&#x26;sid_i=0?utm_source=app.impact.com&#x26;utm_medium=owned-platform&#x26;utm_content=con-350&#x26;utm_campaign=help-center" class="button primary">参加 PXA 课程</a>

*付款组* 可让您为合作伙伴带来的操作设置付款规则，并且包含在您的 [模板条款](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md)中。如果满足某个付款组的条件，该付款组便会在与模板条款 *默认付款*.

规则相同的层级（订单或商品）应用付款变更。每次只能应用 1 个付款组。自定义付款组最好设置为条件互斥；如果付款组的条件有重叠，请将条件更具体的付款组放在顶部（例如“客户状态为新客户且订单总额 ≥ $200”），并将更常见的条件放在底部（例如“订单总额 ≥ $200”）。

## 向模板条款添加付款组

{% hint style="warning" %}
**警告：** 添加额外的付款规则可能需要一定的技术知识。如果您想配置额外的付款规则， [请联系支持团队](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml?execution=e3s1).
{% endhint %}

付款组通常会在创建模板条款时添加，但您之后也可以随时更换合同。

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] → Contracts →** [**Template Terms**](https://app.impact.com/secure/advertiser/engage/contracts/library/view-manage-ios-flow.ihtml).
2. 在右上角，选择 **Create Template Term**.
3. 在 *Event Type*旁边的 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Drop-down menu]**&#x4E2D;，选择此模板条款适用的事件类型。
4. 在 *Payout Groups*旁边，将 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FiZjM1xY8o3v1iR3Zaysd%2FToggle.svg?alt=media\&token=b1550d48-bba9-4e81-8604-bc12370c5caa) **\[Toggle on]** **设置自定义付款组**.
5. 如需添加付款组，请选择 **Add new**.
6. 使用 [*付款规则*](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/how-payout-rules-work.md) 和字段设置付款组的 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-c2cb550b55c51ea1eeff0acbd6f437a03b621a2c%2F60d033ae8a04c14498d5229c3c0160ac05feea7f605dbd770741793c900469f0.svg?alt=media) **\[Drop-down menu]** 。
   * 您也可以选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-6282f271b7521383385339243690b303086736d9%2F3b5a585dd2895bdf1c30d1236c72ba590dddd18717863b27074c8d313d05ae20.svg?alt=media) **\[Add another]** ，在同一个付款组中创建第二条规则。
   * 如果向一个付款组添加多条规则，则必须全部满足，付款组才会生效。
7. 输入 **付款** 金额；如果有此选项，还可以指定应付商品的 **限额** 。

   * 如果在弹窗中看不到 *限额* 开关， [请联系支持团队](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml) ，申请为您的账户启用此功能。

   <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%2Fb7xgieXArFVvI9LuEA2U%2FScreenshot%202026-04-29%20at%2012.15.00.png?alt=media&amp;token=c72612c9-adc0-4f5f-a921-ed55531a36a5" alt="" width="563"><figcaption></figcaption></figure></div>
8. 在弹窗右下角，选择 **添加** 以保存付款组。
9. 如需创建另一个付款组，请选择 **新增**。如果创建多个组，可以选择并拖动它们来更改优先级。

<details>

<summary>优先级的工作方式</summary>

系统会从上到下评估您的佣金组，并应用第一个符合转化条件的组——优先级较低的组都会被跳过。将最具体的条件放在顶部，将较宽泛或兜底的条件放在底部。

例如，针对 **订单总额超过 200 美元的新客户** 的组，必须位于针对 **新客户** 的组之上。如果较宽泛的组优先级更高，它就会先匹配所有新客户订单，使更具体的规则没有机会生效。

</details>

10. 继续 [创建模板条款](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/template-terms/create-template-terms.md).

{% hint style="success" %}
**注意：** 使用以下参数设置佣金组时： *引荐网址* 参数，您可以使用 *通配符* 选项，无论前后是否有其他字符，都能进行匹配。例如，使用 `*facebook*` 可匹配来自 Facebook 的任何引荐网址。
{% endhint %}

### 组合佣金组条件

* 佣金组条件中的逗号不会将两个条件组合起来（例如， `Item Category is ACME, Anvils` 会被解释为“商品类别是 ACME 或 Anvils”）。您可以在包含逗号的规则两侧加上引号来解决此问题（`Item Category is "ACME,Anvils"`).

## 基于地理位置的佣金组

根据地理位置配置佣金组时，您需要选择正确的数据来源。您可以区分点击发起的位置与客户实际居住的位置。

| 要求         | 推荐参数          | 数据来源              |
| ---------- | ------------- | ----------------- |
| 基于收货地址的佣金组 | 客户国家/地区       | 结账时通过您的跟踪像素传递的数据。 |
| 基于点击位置的佣金组 | 由引荐信息推导的国家/地区 | 用户点击时的 IP 地址。     |


---

# 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/platform-features/contracts-and-template-terms/template-terms/payout-adjustments/set-payout-rules-using-payout-groups.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.
