> 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/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).
# Set Up Trademark Bidding Violation Alerts
Take the PXA course
The potential violations alert emails you when impact.com detects potential violations for partners bidding on your trademarks. You won't need to log in and check your search monitoring report daily.
{% embed url="" %}
## Set up potential violations alert
1. From the left navigation bar, select  **Protect** → **Monitoring** → [**Paid Search**](https://app.impact.com/secure/advertiser/protect/fr/compliance-search-monitor.ihtml).
2. In the top-right corner of the screen, select  **\[Email]**.
3. Select  **\[Unchecked box]** **Alert Me**.
4. Set how often you want to receive the email. This can be *Daily*, *Weekly*, or *Monthly*.
5. Set the time when you would like to receive the email.
6. Select **Save**.
* You'll receive an email at the scheduled time listing potential violations you can act on or ignore.
---
# 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/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.