> 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/destinations.md).

# Destination catalog

A destination is a tool that receives your event data. Chord sends it from your storefront or from its servers. Destinations include ad platforms, analytics tools, email and messaging tools, and data warehouses.

Pick a group to see what is available.

* [**Advertising**](/activate/event-streaming/destinations/advertising.md): ad platforms that use your events to measure and optimize campaigns.
* [**Attribution and affiliate**](/activate/event-streaming/destinations/attribution-and-affiliate.md): tools that credit sales to channels, partners and creators.
* [**Analytics**](/activate/event-streaming/destinations/analytics.md): tools that show how shoppers use your store.
* [**Email and marketing**](/activate/event-streaming/destinations/email-and-marketing.md): tools that message your customers.
* [**Personalization**](/activate/event-streaming/destinations/personalization.md): tools that tailor your store to each shopper.
* [**Data warehouses**](/activate/event-streaming/destinations/data-warehouses.md): places to store your events for your own analysis.
* [**Tag managers**](/activate/event-streaming/destinations/tag-managers.md): tools that load other tags on your site.

To add one to your store, see [Connect a destination](/activate/event-streaming/connect-a-destination.md).

{% hint style="info" %}
Chord adds destinations to the catalog over time. If you don't see the one you need, tell the Chord team.
{% endhint %}


---

# 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/destinations.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.