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

# Leapfrogging パス詳細レポート

Leapfrogging Path 詳細レポートは、以下からのドリルスルーレポートです。 [*追い越しコンバージョン詳細レポート*](/brand/ja/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** コンバージョン経路を表示したい注文の [*追い越しコンバージョン詳細レポート*](/brand/ja/what-would-you-like-to-learn-about/platform-features/multi-program-reports/leapfrogging-reports/leapfrogging-conversion-detail-report.md).
   * 選択したフィルターは、〜から引き継がれます *追い越しコンバージョン詳細レポート*.
2. **追加** または **削除** レポートテーブルの列を次の方法で ![](https://1458456015-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>

| 列       | 説明                                                                                                                                    |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| イベント日時  | コンバージョン経路内のイベントの日時。                                                                                                                   |
| パートナー   | Leapfrogging パートナーの名前。                                                                                                                |
| イベントタイプ | 〜の名前 [イベントタイプ](/brand/ja/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/ja/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.