> 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/reach-out-to-partners/partner-groups/active-partner-relationships-with-group-report.md).

# 带有组报告的活跃合作伙伴关系

此报告提供所有具有有效关系的合作伙伴列表，并显示每个合作伙伴的推广活动和组。了解更多关于 [合作伙伴组](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-groups/create-and-manage-partner-groups.md).

#### 访问报告

1. 在左侧导航栏中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 报告 → 更多报告**.
2. 搜索 **带组的活跃合作伙伴关系** 并从报告列表中选择该报告。
3. 查看 *列* 请参阅下面的参考表了解更多信息。

<details>

<summary>列说明</summary>

| 列       | 说明                      |
| ------- | ----------------------- |
| 合作伙伴 ID | 该合作伙伴的唯一 impact.com ID。 |
| 合作伙伴    | 合作伙伴名称。                 |
| 网址      | 与该合作伙伴相关的互联网地址。         |
| 活动 ID   | 该推广活动的唯一 impact.com ID。 |
| 活动      | 推广活动名称。                 |
| 加入日期    | 合作伙伴加入日期。               |
| 组       | 组名称。                    |

</details>

4. 进入报告页面后，您可以使用页面右上角的图标来 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FKG07S1laT6SIusRgHwBA%2FPin.svg?alt=media\&token=1fef79ba-7abe-4eb4-8341-5b33074bee1c) **\[固定]**, ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-5e962e68a3cf6c87d7ade712b204bae70f02fe42%2F07666ee42fc00c5eb99a6545e1f573505a3888c370d4751169eab2b06d01158c.svg?alt=media) **\[计划]**, ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-ec3276f07285180fbb2167a40e148d3e43e8681c%2F05aa88f72076df5a744d4620574f19cc187b7154fe1f3bb73ad7a892b7d23002.svg?alt=media) **\[下载]** 将报告导出为 PDF、Excel 或 CSV 格式，或者 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-b70e3cd0e284da9a2b0f22b7344d6f584a821b55%2F2d250c06ba9e7eee075a038b635153ab7906f3f98d9861020eccac7e0f10b908.svg?alt=media) **\[导出]** 通过 API 导出。

   <div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fk51M3EfpfACt7290rJxK%2FScreenshot%202026-04-24%20at%2013.38.49.png?alt=media&amp;token=edb7f49f-f32e-41a5-84bf-c1d51f07f7ec" alt=""><figcaption></figcaption></figure></div>


---

# 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/reach-out-to-partners/partner-groups/active-partner-relationships-with-group-report.md?ask=<question>&goal=<user_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.
