> 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-promo-code-exception-lists.md).
# 创建促销码例外列表
参加 PXA 课程
优惠码例外列表可用于根据合作伙伴所推动的行为所关联的优惠码，向其支付不同费率。您还可以基于 [商品类别](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists.md) 或 [SKU](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-sku-exception-lists.md).
{% hint style="warning" %}
SKU 和促销代码 [例外列表](https://help.impact.com/brand/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists) 并非在每个 impact.com 版本中都可用。例如，产品驱动增长（PLG）版账户不包含 **SKU** 或 **促销代码** 下的选项 *例外列表*。如果您看不到任一选项，您可能需要升级您的账户。 [联系支持团队](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml).
{% endhint %}
#### 创建优惠码例外列表
1. 在顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧，位于 *例外列表*，选择 [**促销代码**](https://app.impact.com/secure/advertiser/campaign/itemlist/view-promocodeitemlist-flow.ihtml).
3. 选择 **添加新的优惠码例外列表**.
4. 填写以下信息：
| 字段名称 | 说明 |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **列表名称** | 为此列表添加一个名称——它只会内部显示给您和其他账户成员；合作伙伴看不到。 |
| **关联事件类型** | 选择1个或多个事件类型以关联到此例外列表。 |
| **匹配表达式** | \[高级且可选] 输入一个正则表达式以匹配特定的优惠码模式。
请参考这些文章来配置您的正则表达式：
|
5. 选择 **保存并添加项目** 以继续。
6. 您可以添加一个 **促销代码** 或者您可以 **上传CSV或Excel文件** 与您的优惠码一起使用。
* 请参阅 *优惠码例外列表格式* 请参阅下方部分以帮助您构建 .CSV 文件。
7. 选择 **保存**.
* 您现在将在以下位置看到您的新优惠码例外列表： [优惠码例外列表页面](https://app.impact.com/secure/advertiser/campaign/itemlist/view-promocodeitemlist-flow.ihtml).
* 如果您未看到 **促销代码** 选项或此页面，您的版本可能不包含优惠码例外列表。
优惠码例外列表格式
使用下方显示的列名创建 .CSV 或 .XLS/.XLSX 文件：
```programlisting
促销代码
INFL001
INFL002
INFL003
```
| 列 | 类型 | 必填 | 说明 |
| ---- | --- | -- | ----------------------------------------- |
| 促销代码 | 字符串 | 是 | 跟踪转化数据中包含的值。
• 此处输入的值不区分大小写。
|
---
# 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-promo-code-exception-lists.md?ask=&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.
