> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline.md).

# Dataflow Pipeline

The Umbraco Engage package is all about data, data, and more data. To make the most out of this data and do it the most efficient way we have four different stages where the data goes to.

1. [Data collection](/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline/data-collection.md): This is where the visitor data is collected and stored for a moment in the memory of the server.
2. [Data storage](/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline/data-storage.md): This is where the data from memory goes to the database.
3. [Data processing](/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline/data-parsing.md): The data is processed at a later moment to make it more efficient and normalized
4. [Data reporting](/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline/reporting.md): Finally the data is reported within Umbraco Engage

The concept of this Dataflow is the most important concept to grasp when using Umbraco Engage.


---

# 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.umbraco.com/umbraco-engage/17.latest/developers/introduction/dataflow-pipeline.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.