> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/activate/event-streaming.md). # Event streaming Event streaming sends data captured live from your store to the tools your team uses. Chord collects each event once. It then forwards the event to every destination you connect, such as Meta, Google Analytics 4 or Klaviyo. Most destinations receive each event within seconds. Data warehouses, such as BigQuery and Snowflake, load in batches instead. ## How it works Events come from your storefront and your backend. Chord applies your consent settings to each event and sends it on. You manage the whole flow from the CDP page in Chord. On that page you can: * See every connected source and destination. * Watch incoming events and the events sent to each destination. Only admin users can add a destination from the catalog, or edit or delete one. Event streaming is part of Chord. Your team connects destinations when it is ready. {% hint style="info" %} Event streaming sends data live, event by event. To sync audiences or data on a schedule, see [Data activations](/activate/data-activations.md). {% endhint %} ## Where to go next * [**Connect a destination**](/activate/event-streaming/connect-a-destination.md): add a destination from the catalog and turn it on. * [**Browser and server destinations**](/activate/event-streaming/browser-and-server-destinations.md): how the two ways of sending events differ, and why you often want both. * [**Consent**](/activate/event-streaming/consent.md): control which events each destination receives. * [**Property mappings**](/activate/event-streaming/property-mappings.md): send extra event properties to a destination. * [**Functions**](/activate/event-streaming/functions.md): change or filter events before they reach a destination. * [**Deduplication**](/activate/event-streaming/deduplication.md): stop the same event from counting twice. * [**Live Events**](/activate/event-streaming/live-events.md): watch events as they arrive and as they are sent. * [**Notifications**](/activate/event-streaming/notifications.md): get alerts when a destination has errors. * [**Errors and retries**](/activate/event-streaming/errors-and-retries.md): what happens when a destination can't accept an event. * [**Destination catalog**](/activate/event-streaming/destinations.md): every tool Chord can send data to. --- # 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.chord.co/activate/event-streaming.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.