> 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/actions/track-your-conversion-funnel-using-chained-actions.md).
# 使用链式动作跟踪您的转化漏斗
参加 PXA 课程
链式行动可通过链接父行动和子行动来跟踪事件漏斗。此功能适用于希望跟踪包含多个步骤的转化漏斗的品牌。
{% hint style="info" %}
**示例：**
某个合作伙伴推动了试用会员注册（父行动），随后同一客户转化为付费会员（子行动）。impact.com 会跟踪这两个行动及其彼此之间的关系。
一位音乐博主在某个平台上推动了首次订阅（父行动），随后在接下来的几个月中持续续订（子行动）。
{% endhint %}
{% hint style="info" %}
**注意：** 你只能串联在创建账户时已设置的行动。若要串联你现有的行动，请联系 [支持](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml).
{% endhint %}
#### 运作方式
* 父行动会先发生，并且必须先于子行动进行跟踪；否则，你可能会破坏事件链，并且无法将转化归因到相关合作伙伴。
* 子行动通过一个通用客户 ID 与父行动关联，这可确保该转化归因于推动父事件的合作伙伴。只有通过此客户 ID 才能串联行动，并且必须在父行动和子行动中都传递该 ID。
* 如有需要，父行动和子行动都可以单独反向处理。
impact.com 还支持使用链式行动处理包含 2 个或更多事件的多步骤漏斗。请联系 [支持](https://app.impact.com/secure/advertiser/support/customer-support-portal-flow.ihtml) 以获取更多帮助，从而更深入地了解更复杂的链式行动。
{% hint style="info" %}
**注意：** 如需字段示例和可接受参数列表，请参阅 impact.com 的 [字段参考](https://integrations.impact.com/brand-api-reference/reference/action-and-conversion-field-references) 以及模板。我们建议咨询你的 CSM，以确定哪些具体参数最能优化你的 Conversion Data 模板。
{% endhint %}
#### 了解更多
* [修改父事件和子事件类型](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/chained-action-reports/modify-parent-and-child-event-types.md)
* [什么是推荐窗口？](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/chained-action-reports/referral-windows-for-chained-action-reports-explained.md)
* [链式行动报告](/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/chained-action-reports/chained-action-reports.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/brand/zh/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/actions/track-your-conversion-funnel-using-chained-actions.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.