> 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/pt-br/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/introduction-to-paid-search-monitoring.md).
# Introdução ao monitoramento de pesquisa paga
Faça o curso PXA
O Monitoramento de Pesquisa Paga da impact.com permite que as marcas garantam que suas Marcas Registradas estejam protegidas contra lances não autorizados por parceiros em todos os principais mecanismos de busca na maioria dos países/regiões e idiomas. Ele automatiza o processo de monitoramento e correção de violações de pesquisa.
**Faça mais com o Monitoramento de Pesquisa Paga:** Faça upgrade para um pacote pago de palavras-chave para monitorar sua marca no Google, Bing, Yahoo e AOL até 96 vezes por dia. Se você quiser monitorar mais de 50 palavras-chave disponíveis para compra, entre em contato com seu Gerente de Sucesso do Cliente (CSM) ou [entre em contato com o suporte](https://app.impact.com/support/portal.ihtml?createTicket=true).
#### Acessar o monitoramento de pesquisa paga
1. Na barra de navegação à esquerda, selecione  **\[Proteger]**.
2. Selecione **Monitoramento** → **Pesquisa Paga**.
**Para saber mais sobre o Monitoramento de Pesquisa Paga, consulte estes recursos úteis:**
* [Perguntas frequentes sobre Monitoramento de Pesquisa Paga](/brand/pt-br/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/paid-search-monitoring/paid-search-monitoring-faq.md)
* [Criar uma política de Monitoramento de Pesquisa Paga](/brand/pt-br/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)
* [Gerenciar políticas de Monitoramento de Pesquisa Paga](/brand/pt-br/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 parceiros das suas políticas de Monitoramento de Pesquisa Paga](/brand/pt-br/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)
* [Monitorar e revisar anúncios de pesquisa quanto a violações de lances de marca registrada](/brand/pt-br/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 violações de lances de marca registrada](/brand/pt-br/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/pt-br/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.