> 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/introduction-to-paid-search-monitoring.md).
# Introduction à la surveillance de la recherche payante
Suivez la formation PXA
La surveillance des recherches payantes d’impact.com permet aux marques de s’assurer que leurs marques sont protégées contre les enchères non autorisées des partenaires sur tous les principaux moteurs de recherche, dans la plupart des pays/régions et des langues. Elle automatise le processus de surveillance et de remédiation des violations de recherche.
**Faites-en plus avec la surveillance des recherches payantes :** Passez à un forfait de mots-clés payant pour surveiller votre marque sur Google, Bing, Yahoo et AOL jusqu’à 96 fois par jour. Si vous souhaitez surveiller plus de 50 mots-clés disponibles à l’achat, contactez votre Customer Success Manager (CSM) ou [contactez l’assistance](https://app.impact.com/support/portal.ihtml?createTicket=true).
#### Accéder à la surveillance des recherches payantes
1. Dans la barre de navigation de gauche, sélectionnez  **\[Protéger]**.
2. Sélectionnez **écran Monitoring** → **Recherche payante**.
**Pour en savoir plus sur la surveillance des recherches payantes, consultez ces ressources utiles :**
* [FAQ sur la surveillance des recherches payantes](/brand/fr/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/paid-search-monitoring-faq.md)
* [Créer une politique de surveillance des recherches payantes](/brand/fr/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/create-a-paid-search-monitoring-policy.md)
* [Gérer les politiques de surveillance des recherches payantes](/brand/fr/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/manage-paid-search-monitoring-policies.md)
* [Exclure des partenaires de vos politiques de surveillance des recherches payantes](/brand/fr/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/exclude-partners-from-your-paid-search-monitoring-policies.md)
* [Surveiller et examiner les annonces de recherche pour détecter les violations d’enchères sur les marques](/brand/fr/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/review-paid-search-monitoring-results.md)
* [Configurer des alertes de violation d’enchères sur les marques](/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)
---
# 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/introduction-to-paid-search-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.