> 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/action-management/data-feeds/set-up-an-action-event-data-feed-as-a-partner.md).

# 作为合作伙伴设置操作事件数据源

## 设置行动数据馈送

1. 在顶部导航栏中，选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FhyR4iWDS0fO9ZcKFGf82%2FUser%20profile.svg?alt=media\&token=281d8f1b-b9c5-4208-a0a2-a078f54e0eb6) **\[用户资料] → 设置**.
2. 在……下 *技术*，选择 [**数据馈送**](https://app.impact.com/secure/mediapartner/accountSettings/view-edit-daily-feeds-flow.ihtml).
3. 在……旁边 *每日行动馈送*，选择 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FZMLVDhHLGefqRDHaIWTm%2FEdit.svg?alt=media\&token=1f1168ae-5bd3-456c-a366-904d0ecf00cb) **\[编辑]**.
4. 打开开关 ![](https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FEv341AdIiPndQSb7uGMI%2FToggle%20on.svg?alt=media\&token=4ae8972d-c510-4ee2-adc5-e7170981650b) **\[切换]** **启用数据馈送**.
5. 设置 **频率** 以便生成 FTP 文件。
   * 每个文件只会包含自上次生成数据馈送文件以来发生的事件。因此，例如，如果您决定将频率设置为 **每小时**，则只会包含过去每小时内发生的事件。
6. 选择 **数据格式**。您有以下选项：
   * XML：人类和机器都可读的 [标记文本](https://en.wikipedia.org/wiki/XML)
   * TAB：纯文本，使用制表符分隔的值
   * PIPE：纯文本，使用竖线（|）分隔的值
   * CSV：纯文本，逗号分隔的值
7. 选择文件的 **传送方式**.
   * FTP：从 impact.com 的 FTP 服务器拉取行动馈送数据。
   * 合作伙伴 FTP：将行动馈送数据发送到您的服务器——输入必要的服务器详细信息。
   * 电子邮件：用于接收行动数据更新的电子邮件地址。
8. 选择 **保存**.

<details>

<summary>频率选项</summary>

请参阅下表，查看每个选项何时生成文件。所有时间均为 UTC 格式。

| 频率选项   | 生成时间                      |
| ------ | ------------------------- |
| 每小时    | 每天，自上次运行时间以来每小时一次。        |
| 每 2 小时 | 每天，自上次运行时间以来每 2 小时一次。     |
| 每 4 小时 | 每天，自上次运行时间以来每 4 小时一次。     |
| 每 8 小时 | 每天，自上次运行时间以来每 8 小时一次。     |
| 每天两次   | 每天 06:00:00Z 和 18:00:00Z。 |
| 每天     | 每天 02:00:00Z。             |
| 每月     | 每月第一天 03:00:00Z。          |

</details>

<div data-with-frame="true"><figure><img src="https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2FUsWnQkvPvgXq6DzsJaQ4%2FScreenshot%202026-05-23%20at%2013.28.35.png?alt=media&amp;token=a16f953e-d315-4d27-ba0e-53a6e1227e81" alt="" width="527"><figcaption></figcaption></figure></div>

## 数据馈送字段

请在下方链接的电子表格中查看数据馈送文件字段的详细信息。数据馈送文件将始终包含所有标记为 `始终出现在文件中`。标记为 `在有新数据可用时出现` 的字段，如果某一行项目没有新数据可用，则不会出现在文件中。

* 请参阅 [impact.com 行动数据馈送文件数据字段电子表格](https://docs.google.com/spreadsheets/d/1I2VPpe38vFq26Vv-gm_Aqg4mVJv4APJsL9mBSzCXZeU/edit#gid=0) 以获取所有字段的详细信息。


---

# 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/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/action-management/data-feeds/set-up-an-action-event-data-feed-as-a-partner.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.
