> 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/what-would-you-like-to-learn-about/platform-features/action-management/data-feeds/set-up-an-action-event-data-feed-as-a-partner.md).
# Set Up an Action Event Data Feed as a Partner
## Set up an action data feed
1. From the top navigation bar, select  **\[User profile] → Settings**.
2. Under *Technical*, select [**Data Feeds**](https://app.impact.com/secure/mediapartner/accountSettings/view-edit-daily-feeds-flow.ihtml).
3. Next to *Daily Action Feed*, select  **\[Edit]**.
4. Toggle on  **\[Toggle]** **Enable data feed**.
5. Set the **Frequency** in which you want FTP files generated.
* Each file will only include events that happened since the last time a data feed file was generated. So, for example, if you decide to set the frequency to **Hourly**, only events that occurred within each last hour will be included.
6. Select the **Data Format**. You have the following options:
* XML: Human- and machine-readable [markup text](https://en.wikipedia.org/wiki/XML)
* TAB: Plain text, tab-spaced values
* PIPE: Plain text, pipe-separated ( | ) values
* CSV: Plain text, comma-separated values
7. Pick the file's **Delivery Method**.
* FTP: Pull action feed data from impact.com's FTP server.
* Partner FTP: Have action feed data sent to your server — input the necessary server details.
* Email: The email address with which you want to receive action data updates.
8. Select **Save**.
Frequency options
Refer to the table below to see when each selection would generate a file. All times are in UTC format.
| Frequency Option | Generation Times |
| ---------------- | ------------------------------------------------- |
| Hourly | Every day, every hour since the last run time. |
| Every 2 hours | Every day, every 2 hours since the last run time. |
| Every 4 hours | Every day, every 4 hours since the last run time. |
| Every 8 hours | Every day, every 8 hours since the last run time. |
| Twice daily | Every day at 06:00:00Z and 18:00:00Z. |
| Daily | Every day at 02:00:00Z. |
| Monthly | The first day of each month at 03:00:00Z. |
## Data feed fields
See details on the data feed file fields in the linked spreadsheet below. A data feed file will always include all of the fields marked `Always Present in File`. Fields marked `Present when new data is available` won't appear in the file if no new data is available for a given line item.
* Refer to the [impact.com Action Data Feed File Data Fields spreadsheet](https://docs.google.com/spreadsheets/d/1I2VPpe38vFq26Vv-gm_Aqg4mVJv4APJsL9mBSzCXZeU/edit#gid=0) for detailed information on all fields.
---
# 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/what-would-you-like-to-learn-about/platform-features/action-management/data-feeds/set-up-an-action-event-data-feed-as-a-partner.md?ask=&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.
