> 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/promo-codes/regular-expression/match-expression-tool-regex.md).
# 匹配表达式工具正则表达式
当你知道产品 SKU、类别或促销代码中的部分字符组合，并希望将这些字符组合与随转化传入的 SKU、类别或促销代码进行匹配时，就会使用匹配表达式工具。只有在你没有一个完整的项目列表位于一个 [例外列表](/brand/zh/what-would-you-like-to-learn-about/account-administration/program-settings/exception-lists/create-category-and-sku-exception-lists.md).
1. 从顶部导航栏中，选择  **\[用户资料] → 设置**.
2. 在右侧列中，下面 *异常列表*，选择 *异常列表* 部分下，选择 **SKU**.
3. 选择 **添加新的 SKU 列表**.
4. 选择 **显示高级设置** .
5. 在“匹配表达式”字段中，匹配表达式工具有 2 个重要组成部分：
| 组件 | 说明 |
| ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| [括号内的正则表达式](/brand/zh/what-would-you-like-to-learn-about/platform-features/promo-codes/regular-expression/regex-inside-the-parentheses.md) | 与随附的例外列表中的项目完全匹配。 |
| [括号外的正则表达式](/brand/zh/what-would-you-like-to-learn-about/platform-features/promo-codes/regular-expression/regex-outside-the-parentheses.md) | 为例外列表中的项目设置条件，以与传入的转化数据进行匹配。 |
---
# 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/promo-codes/regular-expression/match-expression-tool-regex.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.
