> 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/account-administration/account-settings/send-data-to-impactcom/review-data-connection-submissions.md).

# データ接続の提出内容を確認する

*コネクタ* コネクタは、impact.com とブランド、パートナー、またはその他の関係者間で行われる、すべてのバッチデータファイル転送のためのシステムです。各接続（個々のコネクタ）には、データタイプ（クリック、コンバージョン、商品カタログなど）、方向（受信または送信）、方法（SFTP、FTP、メール）など、いくつかの属性があります。

アカウント設定で、コネクタ経由で送信されたファイルの履歴を確認できます。

1. 上部ナビゲーションバーから、次を選択します ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2F210dEQa93qyQgoJDkieL%2FUser%20profile.svg?alt=media\&token=f84c5b17-fae4-4a30-990a-9de5e57a150b) **\[ユーザープロフィール] → 設定**.
2. 左側の列の下にある *技術*、 **接続**.
3. 接続一覧で、送信内容を確認したい接続にカーソルを合わせ、次を選択します ![](https://1458456015-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-1e0bbc2fbb260c9846c479063dc2a10f301c5a3b%2Ffb08358c10eb18ae39cd472335b74bd43ce45f7c7e5ff705cd708d9d2b84d37d.svg?alt=media) **\[その他]** → **履歴を表示**.

ここから、ファイルを受信した日付、送信が成功したかどうか、ファイルにエラーがあったかどうかなど、各送信に関する詳細情報を表示して絞り込むことができます。


---

# 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/account-administration/account-settings/send-data-to-impactcom/review-data-connection-submissions.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.