> 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/notification-settings/configure-partner-paid-search-monitoring-notification-settings.md).
# 配置合作伙伴付费搜索监控通知设置
付费搜索监控通知会让您及时了解您可能违反品牌条款的任何新增或更新的潜在违规行为。这些通知会显示在左侧导航栏中的通知面板里，并通过电子邮件或短信发送给您。
## 配置您的付费搜索监控通知
1. 在顶部导航栏中，选择  **\[通知]**.
2. 在通知面板的右上角，选择 [**设置**](https://app.impact.com/secure/mediapartner/notification/view-edit-notification-deliverychannel-settings-publisher-flow.ihtml)  **\[下拉菜单]** 以编辑通知设置。
3. 在 *付费搜索监控* 部分，下方的 *违规*下方，选择  **\[下拉菜单]**.
4. 使用  **\[下拉菜单]** 选项，以指定您希望如何以及多频繁接收您所造成的潜在搜索监控违规通知。请参阅下面的 *通知偏好参考* 表，了解这些选项的更多信息。
5. 选择 **保存**.
通知偏好参考
| | |
| ----------- | ---------------------------------------------------- |
| **设置项** | **描述** |
| 事件发生时发送电子邮件 | 每发生一次违规事件，都会向您发送一封电子邮件。 |
| 发送每日摘要邮件 | 当天所有违规事件的单封每日摘要通知将通过电子邮件发送给您。 |
| 发送每周摘要邮件 | 本周所有违规事件的单封每周摘要通知将通过电子邮件发送给您。 |
| 发送短信 | 每次违规通知都会向已验证的手机号码发送一条短信。 |
| 特定设置（高级） | 您可以选择每 *新* 或 *更新后的* 次违规的通知方式。您还可以为 *严重* 违规设置不同的通知选项。 |
| 不发送通知 | 不会发送任何通知。 |
---
# 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/partner/zh/ni-xiang-liao-jie-shen-me/account-management/account-settings/notification-settings/configure-partner-paid-search-monitoring-notification-settings.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.