# Data

> Get your Grovs events out: stream them live to a webhook, a bucket or a pull feed, and export history as files.

Source: https://docs.grovs.io/docs/data

Both live in **Developers → Data Export**. They need an active paid plan on Grovs Cloud, or a self-hosted Enterprise deployment.

- [Event stream](https://docs.grovs.io/docs/data/event-stream): Send every analytics and purchase event to a webhook or an S3-compatible bucket as it happens, or read them from a pull feed.
- [Exports](https://docs.grovs.io/docs/data/exports): Export historical events as a file or through a destination, and export links and segment members as CSV.

## Which one to use

| You want to                                                            | Use                                                                                                 |
| ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| React to installs, opens or purchases in your backend within seconds   | A webhook [destination](https://docs.grovs.io/docs/data/event-stream#add-a-webhook-destination)     |
| Load every event into Snowflake, Databricks or BigQuery                | An S3 [destination](https://docs.grovs.io/docs/data/event-stream#add-an-s3-destination)             |
| Poll for events from your own job, at your own pace                    | The [pull feed](https://docs.grovs.io/docs/data/event-stream#read-the-pull-feed)                    |
| Get events from before you connected, or fill a gap longer than 7 days | An [event export](https://docs.grovs.io/docs/data/exports#events)                                   |
| Hand a list of users to another team or tool                           | A [segment export](https://docs.grovs.io/docs/analytics/segments/members-and-exports#export-to-csv) |

To read the pull feed from code, see the [Event stream API](https://docs.grovs.io/docs/api-reference/event-stream).