> 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/platform-features/reporting-for-partners/report-management/save-reports-as-a-partner.md).
# 作为合作伙伴保存报告
参加 PXA 课程
在查看任何报告时，您可以使用提供的筛选器编辑默认视图，并将该视图保存供将来参考。如果您经常希望在特定时间范围内或在应用特定筛选条件的情况下查看报告数据，这将很有用。
## 保存报告
1. 在顶部导航栏中，选择 **报表 →** **更多报告**.
* 或者，在顶部导航栏中，选择 **报告** **→ 更多 → 更多报表**.
2. 将鼠标悬停在您想查看的任意报告上，然后选择 **查看**.
3. 在报告中，使用筛选器自定义所显示的数据，然后选择 **应用**.
4. 在报告名称旁边，选择 **保存**.
5. 在 *保存视图* 在窗口中，填写：
| 选项 | 描述 |
| -- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 名称 | 为此已保存的视图添加一个描述性名称。 |
| 默认 | 
\[开启切换开关] 默认 以 将其设为此报告的默认视图.
此已保存视图将成为此报告类型的新默认视图。您始终可以从 更多 报告 界面将您归入了哪个归因组。
|
| 公开 | \[开启切换开关] 公开 以 使此视图对该账户的其他用户可用.
如果报告设置为公开，它将会显示给其他用户，位于 报告 → 已保存的报告.
|
6. 选择 **保存**.
## 查看您已保存的报告
1. 在顶部导航栏中，选择 **报告** → [**已保存的报告**](https://app.impact.com/secure/mediapartner/MP_Saved_Scheduled_Report/Saved/report/pSavedReports.ihtml).
2. 选择您要查看的已保存报告的报告名称。
* 了解如何 [管理您已保存的报告](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/reporting-for-partners/report-management/manage-saved-reports-as-a-partner.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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/reporting-for-partners/report-management/save-reports-as-a-partner.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.
