> 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/protect-and-monitor-your-performance-program/promo-code-monitoring/log-a-promo-code-monitoring-violation.md).
# 记录促销代码监控违规
参加 PXA 课程
1. 从左侧导航菜单中，选择  **\[保护]** → **监控 → 优惠码**.
2. 在……上 *优惠码监控* 屏幕，找到您想要为其记录违规的优惠码，然后选择 **审核**.
3. 前往 *决定* 部分，然后使用下拉菜单设置 *结果* 进行 **违规**.
4. 填写 *违规信息* 部分：
违规信息参考
| | |
| -------- | -------------------------------------------------------------------------------------------------- |
| **错误** | 使用下拉菜单选择此违规所涉及的错误。 |
| **错误原因** | 使用下拉菜单选择记录此违规的错误原因。 |
| **严重程度** | 使用下拉菜单指示此违规的严重程度——通常，越严重的违规表示应尽快解决。 |
| **到期日** | 使用日历和时间下拉菜单来指示合作伙伴解决违规的截止日期。 |
| **附件** | 如有相关内容，请使用 *选择文件* （或拖放）与此违规相关的文件（例如，违规本身的截图）。 |
| **备注** | 使用文本字段添加有关此违规的评论。当设置为 **公开**时，所有相关方（即合作伙伴、您以及其他账户成员）都可以看到它。当设置为 **私密**时，只有您和您的其他账户成员（不是合作伙伴）可以看到它。 |
5. 完成后，选择 **创建违规** 位于屏幕底部。
#### 自动创建违规
您可以设置您的政策，在优惠码过期或未经授权时自动创建违规并分配给合作伙伴。
1. 从左侧导航菜单中，选择  **\[保护]** → **监控 →** **政策**.
2. 在右上角附近，选择 **创建政策**.
3. 选择 **优惠码监控 → 开始使用**.
4. 为您的政策命名，并将您的品牌名称添加为搜索词。
5. 勾选  **\[复选框]** **如果签约合作伙伴推广的优惠码符合以下条件，则自动创建违规：\[搜索词]**.
6. 选中后，将出现一个下拉菜单，您可以从中选择为以下情况设置自动创建违规： *已到期* 和 *未授权* 代码。
7. 选择 **下一步**.
8. 选择  **\[复选框]** 在您想纳入该政策的所有优惠码旁边，然后选择 **下一步**.
9. 审核您的政策，然后选择 **保存**.
了解更多关于 [创建和管理政策](/brand/zh/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/promo-code-monitoring/guide-to-promo-code-monitoring.md#create-and-manage-policies).
---
# 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/protect-and-monitor-your-performance-program/promo-code-monitoring/log-a-promo-code-monitoring-violation.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.