> 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/paid-search-monitoring/set-up-trademark-bidding-violation-alerts.md).
# 设置商标竞价违规提醒
参加 PXA 课程
潜在违规提醒会在 impact.com 检测到合作伙伴对您的商标进行竞价时向您发送电子邮件。您无需每天登录并查看搜索监控报告。
{% embed url="" %}
## 设置潜在违规提醒
1. 在左侧导航栏中，选择  **保护** → **监控** → [**付费搜索**](https://app.impact.com/secure/advertiser/protect/fr/compliance-search-monitor.ihtml).
2. 在屏幕右上角，选择  **\[电子邮件]**.
3. 选择  **\[未选中复选框]** **提醒我**.
4. 设置您希望接收电子邮件的频率。可以是 *每天*, *每周*，或 *每月*.
5. 设置您希望接收电子邮件的时间。
6. 选择 **保存**.
* 您将在预定时间收到一封电子邮件，其中列出您可以处理或忽略的潜在违规。
---
# 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/paid-search-monitoring/set-up-trademark-bidding-violation-alerts.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.