> 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/multi-program-reports/leapfrogging-reports/leapfrogging-path-detail-report.md).
# Leapfrogging 路径详情报告
跳转路径明细报告是一个可下钻报表，来自 [*超越转化明细报告*](/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md)。此报表会为您显示您在其中所选订单的转化路径的更多详细信息 *超越转化明细报告*.
#### 访问报告
{% hint style="warning" %}
This feature is only available with specific impact.com editions or add-ons. If you see the .svg?alt=media\&token=91ff61f9-8618-4503-b0df-791e0353d124) **Optimize** icon, your account is eligible for the upgrade. Select the icon and get the Optimize add-on directly in the platform!
{% endhint %}
1. 选择 **订单 ID** 中您想查看其转化路径的订单的 [*超越转化明细报告*](/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md).
* 您所选的筛选条件将从 *超越转化明细报告*.
2. **添加** 或 **移除** 使用  **\[列]** 图标从报告表中添加或移除列，位于报告右上角。
* 请参阅下面的 *报告列参考* 以了解有关报告中显示数据的更多信息。
报告列参考
| 列 | 描述 |
| ------- | ------------------------------------------------------------------------------------------------------------------------ |
| 事件日期 | 转化路径中该事件的时间和日期。 |
| 合作伙伴 | 跳转合作伙伴的名称。 |
| 事件类型 | 的名称 [事件类型](/brand/zh/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md) ，用于跟踪转化。 |
| 广告名称 | 在转化路径中引发此事件的广告名称。 |
| Ref URL | 此事件流量来源的引荐 URL。 |
---
# 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/multi-program-reports/leapfrogging-reports/leapfrogging-path-detail-report.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.