> 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/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists.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>

类别例外列表可让您根据与某个操作关联的类别向合作伙伴支付不同的费率。

**我什么时候会使用此功能？**

* **潜在客户开发：** 可针对希望根据人口统计特征调整支付金额的潜在客户开发活动实施基于类别的支付。例如，与其他国家相比，您的业务可能对来自美国的客户有更高的线索转化率。此时，您可以决定为美国客户的线索分配更高的类别支付金额。

## 创建类别例外列表

1. 从顶部导航栏中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[用户资料] → 设置**.
2. 在……中 *项目* 列，滚动到 *异常列表* 并选择 [**类别**](https://app.impact.com/secure/advertiser/campaign/itemlist/view-categoryitemlist-flow.ihtml).
3. 在右上角，选择 **添加新的类别列表**.
4. 填写以下信息：

   <table><thead><tr><th width="269.796875">字段</th><th>说明</th></tr></thead><tbody><tr><td><strong>列表名称</strong></td><td>为此列表添加一个名称——它只会在您和其他账户成员内部显示；合作伙伴不会看到。</td></tr><tr><td><strong>关联事件类型</strong></td><td>选择一个或多个事件类型与此异常列表关联。</td></tr><tr><td><strong>匹配表达式</strong></td><td><strong>[高级和可选]</strong> 通过指定带有 1 个分组的正则表达式，使系统能够匹配类别值的一部分。分组所表示的值将与此列表中的类别值进行匹配。如果您有使用正则表达式的场景，但不确定如何配置， <a href="https://app.impact.com/support/portal.ihtml?createTicket=true&#x26;">联系支持团队</a>.</td></tr></tbody></table>
5. 选择 **保存并添加项目** 以继续。
6. 您可以添加 **类别** 以及可选的 **显示值** 使用界面中的字段，或者您也可以 **上传 CSV 或 Excel 文件** 以及您的类别。
7. 在添加项目或上传文件后，选择 **保存** 以完成该流程。您现在将在以下位置看到新的类别例外列表： *类别列表* 界面中进行设置。

<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%2FvD0JEUv4z5YD7AUe5UWk%2FScreenshot%202026-04-21%20at%2018.06.48.png?alt=media&amp;token=62ec3787-adaa-40af-b107-262e328037d0" alt="" width="563"><figcaption></figcaption></figure></div>

## 类别例外列表格式

使用下面的两个列名创建一个 .CSV 或 .XLS/.XLSX 文件。

<table><thead><tr><th width="170.484375">列</th><th width="169.7734375">类型</th><th width="169.9453125">必填</th><th>说明</th></tr></thead><tbody><tr><td>类别</td><td>字符串</td><td><strong>是</strong></td><td>包含在转化跟踪数据中的值。</td></tr><tr><td>显示值</td><td>字符串</td><td>否</td><td>如果您希望在报表中显示不同的值，请输入显示值。例如，如果类别值是某种计算机生成的值，那么您可能希望输入显示值，以便在报表中更容易理解。</td></tr></tbody></table>

**例如：**

```programlisting
类别，显示值
新产品，最新发布
```

通常，支付费率基于商品类别；不过，您也可以为特定商品设置支付费率。对于您希望具有特定支付金额的每个商品，都需要创建一个商品类别。在创建模板条款时，您需要为每个类别列表指定支付费率。与某个类别列表关联的所有类别名称都将根据合同享有相同的支付费率。


---

# 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/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists.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.