> 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/zh/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/web-monitoring/review-web-monitoring-results.md).
# 查看网页监控结果
Web Monitoring 可帮助您的品牌追踪推广位置，并识别风险——例如品牌安全问题或未经批准的术语——这些风险可能损害您的声誉或导致合规违规。impact.com 会监控合作伙伴的数字渠道，包括网站、电子邮件和社交媒体，分析数据中的风险，并让您审查投放，以发现潜在的品牌安全和合规问题。
如果您的账户已设置 Web Monitoring，您就可以查看被标记的合作伙伴帖子，并在需要时进行处理。了解如何 [设置 Web Monitoring](/brand/zh/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/web-monitoring/create-a-web-monitoring-policy.md).
1. 从左侧导航菜单中，选择  **\[保护]** **→ 监控 → Web**.
* 此页面显示您的所有 Web Monitoring 结果列表。
2. 您也可以使用页面顶部的筛选条件来缩小结果范围。
筛选条件说明
| 筛选器 | 说明 |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 日期范围 | 选择您要查看结果的日期范围。 |
| 合作伙伴 | 按名称搜索合作伙伴，或浏览列表选择一个或多个合作伙伴。 |
| 属性 | 按名称搜索媒体资源，或浏览列表选择一个或多个媒体资源。 |
| 政策 | 查看与特定政策相关的结果。 |
| 状态 | 查看 *新建*, *已忽略*, *已忽略域名*，或 *已归档* 结果。 |
| 问题 | 查看存在一个或多个问题的结果：
• 品牌安全
• 未经批准的术语
• 失效链接
• 无效链接
• 未披露
|
| 合作伙伴类型 | 将结果限制为 **已签约合作伙伴**, **未签约合作伙伴**，或 **非 impact.com 合作伙伴**. |
3. 将光标悬停在某个结果上，然后选择 **查看** 以查看与此结果相关的帖子和提及。
4. 将光标悬停在某个帖子上，然后选择 **查看** 以查看已被标记的帖子。
* 该 **内容审核** 面板中包含提及和问题列表。
* 帖子本身也会被标注。
---
# 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/zh/what-would-you-like-to-learn-about/platform-features/protect-and-monitor-your-performance-program/web-monitoring/review-web-monitoring-results.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.