> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/integrations/datasyncs/configure-a-datasync-export.md).

# Configure a Data Syncs Export

HockeyStack allows you to export your data from Hockeystack to external systems for advanced analysis, reporting, and activation. Exports are designed to support both go to market teams that want clean, business ready datasets and data science and engineering teams that need full fidelity event level data.

To do so, we currently offer a single type of data export:

**Stage Data Export** is designed to deliver the most relevant, analysis ready data for reporting and decision making. It returns actions that map to a defined stage or touchpoint in your Data Categorization settings, ensuring the dataset stays focused on what matters most.

{% content-ref url="/pages/xwe3RUohr7TBYsj2aQic" %}
[Stage Data Export Schema](/integrations/datasyncs/configure-a-datasync-export/stage-data-export-schema.md)
{% endcontent-ref %}

The authentication method for data exports is the same as the data imports and is outlined below:

{% content-ref url="/pages/Rc0GacoPda50jUhbtNEG" %}
[Connecting your Warehouse](/integrations/datasyncs/connecting-your-warehouse.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/integrations/datasyncs/configure-a-datasync-export.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 `build a script that syncs our docs to a CMS` 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.