> 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/deals/view-deal-performance-data.md).

# ディールのパフォーマンスデータを表示

Dealのパフォーマンスデータを確認するには、次の2つのレポートを使用できます：

{% tabs %}
{% tab title="案件別パフォーマンス" %}
この *案件別パフォーマンス* このレポートでは、Dealごとに集計されたパフォーマンスデータが表示されます。プログラムにとって最も成果の高いDealだけを見たい場合は、このレポートを使用してください。

{% hint style="info" %}
**注：** 次を [Deal別パフォーマンスレポート](/brand/ja/what-would-you-like-to-learn-about/platform-features/multi-program-reports/performance-reports-for-brands/performance-by-deal-report.md#manage-the-report-0-0) さらなる洞察などに。
{% endhint %}
{% endtab %}

{% tab title="高度なアクション一覧" %}
この *高度なアクション一覧* このレポートではさまざまなデータポイントを表示でき、特定のDealのパフォーマンスデータにさらに文脈を加えるのに役立ちます（以下の *契約* フィルター）。詳しくは [レポートの場所](/brand/ja/what-would-you-like-to-learn-about/platform-features/multi-program-reports/performance-reports-for-brands/advanced-action-listing-report.md).

{% hint style="info" %}
**注：** 次を [詳細アクション一覧レポート](/brand/ja/what-would-you-like-to-learn-about/platform-features/multi-program-reports/performance-reports-for-brands/advanced-action-listing-report.md) さらなる洞察などに。
{% endhint %}
{% endtab %}
{% endtabs %}


---

# 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/deals/view-deal-performance-data.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.