> 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/declined-insertion-orders-report-for-partners.md).
# 合作伙伴已拒绝的插入订单报告
该 **已拒绝的插入订单报告** 向您展示自您使用 impact.com 以来所有被拒绝的合同。本报告将显示您所属的项目、合同（以前称为 *插入订单*）、拒绝日期和拒绝原因。
1. 在顶部导航栏中，选择  **\[搜索]**，然后输入“已拒绝的插入订单”。
2. 在 *报告* 列下，选择 [**已拒绝的插入订单**](https://app.impact.com/secure/mediapartner/viewReport.report).
3. 在这里，您可以查看被拒绝的合同信息。
| 列 | 描述 |
|---|
| 广告活动 | 查看该被拒绝合同所属的项目。 |
| 插入订单 | 查看被拒绝合同所遵循的模板条款名称。 |
| 拒绝日期 | 查看合同被拒绝的日期。 |
| 拒绝原因 | 查看合同被拒绝的原因（如果提供了原因）。 |
---
# 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/declined-insertion-orders-report-for-partners.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.
