> 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/actions-and-payouts/chained-action-reports/chained-action-reports.md).
# 链式动作报告
有 3 个报告专门使用链式操作数据： *高级操作列表*, *活动漏斗*，以及 *链式操作列表*.
#### 高级操作列表
如果您想查看特定客户及其关联的所有事件，Advanced Action Listing 会很有用。为此，您将使用 *Customer ID* 筛选器。
您可以按照以下步骤查找该客户的报告和转化数据：
1. 在左侧导航栏中，选择  **\[Engage] → 报告 → 更多报告**.
2. 在 *类别* 搜索栏旁边的筛选器中，选择 **绩效**.
3. 选择 **高级操作列表** 以查看报告。
4. 选择 *客户 ID* 筛选器并输入您想查看转化数据的客户 ID。
#### 活动漏斗
Campaign Funnel 报告会按点击来源日期汇总，显示每个漏斗层级的对话数量。该报告不会将已撤销操作与可执行操作区分开。
您可以使用屏幕右上角的按钮，对在此创建的任何报告进行计划、保存或检索（通过 API）。
1. 在左侧导航栏中，选择  **\[Engage] → 报告 → 更多报告**.
2. 在 *类别* 搜索栏旁边的筛选器中，选择 **绩效**.
3. 选择 **漏斗表现** 以查看报告。
4. 导航到事件类型列（例如， *销售*）并选择该值。
* 您将下钻到 Campaign Funnel 报告 - 按最后点击日期划分的转化列表。
#### 链式操作列表
Chained Action Listing 报告会显示给定一组父子链式操作的链式操作列表。
您可以 **安排**, **保存**，或 **检索** 通过 API 检索您在此创建的任何报告，使用屏幕右上角的按钮。
1. 在左侧导航栏中，选择  **\[Engage] → 报告 → 更多报告**.
2. 在 *类别* 搜索栏旁边的筛选器中，选择 **列表**.
3. 选择 **链式操作列表** 以查看报告。
4. 在报告标题下，设置您的筛选器并选择  **\[搜索]**.
* 您可以选择 **显示** 并选择 *Shared Id、SubId1、SubId2 或 SubId3* 以查看相关信息。
---
# 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/actions-and-payouts/chained-action-reports/chained-action-reports.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.
.png?alt=media&token=978e5a44-4e86-4424-9c94-048e6aec999e)