> 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 路径详情报告

跳跃式转化路径详情报告是一个钻取报告，可从以下报告进入： [*跳跃式转化详情报告*](https://help.impact.com/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 ![](https://1651675991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpVKEIcehMut8QKRmaUZu%2Fuploads%2F5ikfGgRSMOFn089EEFxy%2Foptimize.svg%20\(1\).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** ，即您想要查看其转化路径的订单的 ID，该订单位于  [*跳跃式转化详情报告*](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md).
   * 您在以下报告中选择的筛选条件将保留： *跳跃式转化详情报告*.
2. **使用** 或 **移除** 报表表格中的列。 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2FxFDYIXnntoj76xzm1CXr%2FColumns.svg?alt=media\&token=001578cd-38da-4ecc-98e9-f8f461e61ff2) **【列】** 图标，该图标位于报告的右上角。
   * 如需详细了解报告中显示的数据，请参阅下方的 *报告列参考* 。

<details>

<summary>报告列参考</summary>

| 列      | 说明                                                                                                                                             |
| ------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| 事件日期   | 转化路径中事件发生的时间和日期。                                                                                                                               |
| 合作伙伴   | 跳跃式转化合作伙伴的名称。                                                                                                                                  |
| 事件类型   | 跟踪该转化的 [事件类型](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md) 的名称。 |
| 广告名称   | 触发转化路径中此事件的广告名称。                                                                                                                               |
| 引荐 URL | 此事件流量来源的引荐 URL。                                                                                                                                |

</details>


---

# 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=<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.
