> 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/es/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).
# Configurar alertas de violación de pujas por marca
Realiza el curso de PXA
Las alertas de posibles infracciones te envían un correo electrónico cuando impact.com detecta posibles infracciones de socios que pujan por tus marcas registradas. No tendrás que iniciar sesión y revisar tu informe de monitoreo de búsqueda a diario.
{% embed url="" %}
## Configurar alerta de posibles infracciones
1. En la barra de navegación izquierda, seleccione  **Proteger** → **Monitoreo** → [**Búsqueda pagada**](https://app.impact.com/secure/advertiser/protect/fr/compliance-search-monitor.ihtml).
2. En la esquina superior derecha de la pantalla, selecciona  **\[Correo electrónico]**.
3. Seleccione  **\[Casilla sin marcar]** **Avísame**.
4. Configura con qué frecuencia quieres recibir el correo electrónico. Puede ser *Diario*, *Semanal*, o *Mensual*.
5. Configura la hora en la que te gustaría recibir el correo electrónico.
6. Seleccione **Guardar**.
* Recibirás un correo electrónico a la hora programada con una lista de posibles infracciones sobre las que puedes actuar o ignorar.
---
# 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/es/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.