> 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/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-path-detail-report.md).

# Leapfrogging Path Detail Report

The Leapfrogging Path Detail Report is a drill-through report from the [*Leapfrogging Conversion Detail Report*](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md). This report shows you more details about the conversion path for the order you selected in the *Leapfrogging Conversion Detail Report*.

#### Access the report

{% 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. Select the **Order ID** of the order you want to view the conversion path for in the [*Leapfrogging Conversion Detail Report*](/brand/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md).
   * Your chosen filters will persist from the *Leapfrogging Conversion Detail Report*.
2. **Add** or **remove** columns from the report table using the ![](https://4048883401-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) **\[Columns]** icon at the top-right of the report.
   * See the *Report column reference* below for more information on the data displayed in the report.

<details>

<summary>Report column reference</summary>

| Column     | Description                                                                                                                                                 |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Event Date | The time and date of the event in the conversion path.                                                                                                      |
| Partner    | The name of the leapfrogging partner.                                                                                                                       |
| Event Type | The name of the [event type](/brand/what-would-you-like-to-learn-about/platform-features/event-types/event-types-explained.md) that tracked the conversion. |
| Ad Name    | The name of the ad that caused this event in the conversion path.                                                                                           |
| Ref URL    | The referring URL from which this event traffic originated.                                                                                                 |

</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/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.
