> 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/promo-code-monitoring.md).
# 促销代码监控
参加 PXA 课程
该 *优惠码监测* 界面提供对 impact.com 在您的政策中所包含的优惠码所发现数据的洞察。
1. 从左侧导航菜单中，选择  **\[Protect] → 监测 →** [**促销码**](https://app.impact.com/secure/advertiser/protect/fr/compliance-promo-code-monitor.ihtml?u=%2Fsecure%2Fcompliance%2Fdata%2Fcompliance-promo-code-monitor-flow.ihtml).
在界面上会汇总发现正在推广这些优惠码的合作伙伴，以及联盟客和其他媒体来源（包括非 impact.com 合作伙伴）。
#### 管理优惠码状态
1. 在……上 *优惠码监测* 屏幕上，选择  **\[复选框]** 位于优惠码旁边。
2. 选择 **更改状态**，然后选择状态。
* 请参阅以下状态说明：
| 状态 | 说明 |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |
| **设为“新”** | 将优惠码列表标记为 *新建*。状态为“新”的优惠码会显示在以下位置的默认视图中： *优惠码监测* 界面，如果它已关联到某个合作伙伴。 |
| **归档广告** | 将优惠码列表标记为 *已归档*。这将使这些优惠码在以下位置的默认视图中隐藏： *优惠码监测* 界面中进行设置。 |
| **忽略列表** | 将优惠码列表标记为 *已忽略*。这将使这些优惠码在以下位置的默认视图中隐藏： *优惠码监测* 界面。将来看到的任何这些特定优惠码都将被标记为 *已忽略* ，并且不会显示在界面上，除非您将状态更改为 *已归档* 或 *新建*. |
| **忽略列表域名** | 将所有关联到合作伙伴域名的优惠码标记为 *已忽略*。这将使这些优惠码列表在以下位置的默认视图中隐藏： *优惠码监测* 界面。将来看到的任何与此域名关联的这些特定优惠码都将被标记为 *已忽略* ，并且不会显示在界面上，除非您将状态更改为 *已归档* 或 *新建*. |
| **移除域名忽略列表** | 从忽略列表中移除所有关联到合作伙伴域名的优惠码。这将被标记为 *已归档* ，并且不会显示在界面上，除非用户将状态更改为 *新建*. |
**了解优惠码列表标签**
一个 *标签* 将为每个优惠码列表添加额外信息标签（例如， *已到期*, *未授权*）。根据这些信息，您可以将其设置为 *已归档*, *忽略列表*，或记录违规。
---
# 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/promo-code-monitoring.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.
