> 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/fr/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).
# Configurer des alertes de violation d’enchères sur les marques
Suivez la formation PXA
L’alerte de violations potentielles vous envoie un e-mail lorsque impact.com détecte des violations potentielles de la part de partenaires enchérissant sur vos marques. Vous n’aurez pas besoin de vous connecter et de vérifier chaque jour votre rapport de suivi des recherches.
{% embed url="" %}
## Configurer l’alerte de violations potentielles
1. Dans la barre de navigation de gauche, sélectionnez  **Protéger** → **écran Monitoring** → [**Recherche payante**](https://app.impact.com/secure/advertiser/protect/fr/compliance-search-monitor.ihtml).
2. Dans le coin supérieur droit de l’écran, sélectionnez  **\[E-mail]**.
3. Sélectionnez  **\[Case non cochée]** **M’alerter**.
4. Définissez la fréquence à laquelle vous souhaitez recevoir l’e-mail. Cela peut être *Quotidien*, *Hebdomadaire*, ou *Mensuel*.
5. Définissez l’heure à laquelle vous souhaitez recevoir l’e-mail.
6. Sélectionnez **Enregistrer**.
* Vous recevrez un e-mail à l’heure prévue listant les violations potentielles sur lesquelles vous pouvez agir ou que vous pouvez ignorer.
---
# 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/fr/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.