> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/event-management/event-data-extract.md).

# Export Event Data

## Overview

This document introduces how to obtain all event data that occurred on a specific date.

## Procedure

![Check the Export Event Data button](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-1892735d662d6c4dca1671a15edd0659ec9c5a1a%2F4721cc8-_2022-04-26_14.15.04_fff2b49d05246384.png?alt=media)

1. Click the **`𝌀` button** in the upper right area of the event list, then click **`Export Event Data`**.
2. A dialog for selecting a date appears. Select the desired date.
3. Click the **`Export`** button in the dialog.
4. An email containing a link to download the event data is sent.

## Notes

* Data for **all events** on the selected date is exported.
* Both the Development Environment and Production Environment are exported.
* While export is in progress, clicking the Export Event Data button again will not initiate a new export. Check the data from the previous export attempt first.


---

# 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://docs.hackle.io/en/event-management/event-data-extract.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.
