> 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/zh/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://1186853034-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://1186853034-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/zh/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.