> 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/submit-and-modify-conversion-data/discover-conversion-data-errors.md).

# コンバージョンデータのエラーを確認

修正内容を送信する一般的な理由の1つは、誤ったコンバージョンデータが impact.com に報告されていたことに気づいた場合です。各アクションについて受信したコンバージョンデータを確認し、自身のシステム内のデータと比較できます。

#### 保留中の支払いを表示

1. 左側のナビゲーションメニューから、次を選択します ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → トランザクション → 保留中の報酬 → アクション**.
2. ここから、 [保留中の支払いを確認できます](/brand/ja/what-would-you-like-to-learn-about/platform-features/actions-and-payouts/payouts/filter-and-download-pending-payouts-list.md).
   * この画面では、すべての保留中のアクションに関する情報が表示されます。たとえば、そのアクションが発生したと報告された日時、プロモコードが使用されたかどうかなどです。また、アクションの *アクションID* を選択すると、報告されている場合はコンバージョン経路のタイムラインも含め、アクションに関するさらに詳しい情報を表示できます。


---

# 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/submit-and-modify-conversion-data/discover-conversion-data-errors.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.