> 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/introduction-to-paid-search-monitoring.md).
# Introducción al monitoreo de búsqueda de pago
Realiza el curso de PXA
El Monitoreo de búsqueda pagada de impact.com permite a las marcas asegurarse de que sus marcas registradas estén protegidas contra pujas no autorizadas por parte de socios en todos los principales motores de búsqueda en la mayoría de los países/regiones e idiomas. Automatiza el proceso de supervisar y solucionar infracciones de búsqueda.
**Haga más con el Monitoreo de búsqueda pagada:** Actualice a un paquete de palabras clave de pago para supervisar su marca en Google, Bing, Yahoo y AOL hasta 96 veces al día. Si desea supervisar más de las 50 palabras clave disponibles para la compra, póngase en contacto con su Customer Success Manager (CSM) o [contacta con soporte](https://app.impact.com/support/portal.ihtml?createTicket=true).
#### Acceda al monitoreo de búsqueda pagada
1. En la barra de navegación izquierda, seleccione  **\[Proteger]**.
2. Seleccione **Monitoreo** → **Búsqueda pagada**.
**Para obtener más información sobre el Monitoreo de búsqueda pagada, consulte estos recursos útiles:**
* [Preguntas frecuentes sobre el Monitoreo de búsqueda pagada](/brand/es/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/paid-search-monitoring-faq.md)
* [Crear una política de Monitoreo de búsqueda pagada](/brand/es/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)
* [Gestionar políticas de Monitoreo de búsqueda pagada](/brand/es/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/manage-paid-search-monitoring-policies.md)
* [Excluir socios de sus políticas de Monitoreo de búsqueda pagada](/brand/es/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)
* [Supervisar y revisar anuncios de búsqueda para detectar infracciones de pujas sobre marcas registradas](/brand/es/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/review-paid-search-monitoring-results.md)
* [Configurar alertas de infracciones de pujas sobre marcas registradas](/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)
---
# 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/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.