> 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/connect-a-destination.md).

# Connect a destination

Add a destination from the catalog in Chord, then connect it to a source. Chord starts sending events as soon as the connection is on.

{% hint style="warning" %}
Before you connect a destination, turn off the same destination's own tracking in your store or in the vendor's tool. Ask each destination owner to confirm. For example, if you add Meta Pixel in Chord, remove the Meta Pixel from your theme and from Google Tag Manager.

Running a tool's own tracking next to the same destination in Chord can send duplicate events downstream.
{% endhint %}

Only admin users can add, edit or delete destinations.

## Add the destination

1. In Chord, go to **CDP**.
2. On the **Overview** tab, click **Add** next to Destinations.
3. Choose the destination from the catalog.
4. Enter a **Destination Name** and the settings the destination asks for. Each destination page in the [catalog](/activate/event-streaming/destinations.md) lists them.
5. Optionally set **Environment** (Production or Staging) and **Direction** (Front-end or Back-end). These tags help you tell similar destinations apart.
6. Under **Consent Requirements**, choose the [consent categories](/activate/event-streaming/consent.md) the destination needs. See the warning below.
7. If you see a **Test Connection** button, click it and wait for **Connection Successful**.
8. Click **Create**.

{% hint style="warning" %}
Chord only applies consent to destinations that have at least one consent category. A destination with no category receives every event, including events from visitors who declined consent. Set the categories before you turn the destination on.
{% endhint %}

## Connect it to a source

A new destination doesn't receive events until you connect it to a source, such as your storefront or your backend.

1. On the **Overview** tab, find the destination and open its menu.
2. Click **Connect**.
3. Under **Select source to connect**, choose the source.
4. Leave **Connection Enabled** on.
5. Optionally set an **Events Allowlist**, [property mappings](/activate/event-streaming/property-mappings.md) and a [functions](/activate/event-streaming/functions.md) pipeline.
6. Save the connection.

The **Events Allowlist** only applies to [browser destinations](/activate/event-streaming/browser-and-server-destinations.md). Functions only apply to server destinations. To limit events on a server destination, use a function.

Many destinations come in two versions, one for the browser and one for the server. Connect both for the best results. See [Browser and server destinations](/activate/event-streaming/browser-and-server-destinations.md).

## Check that it works

Open **Live Events** and look for your events. See [Live Events](/activate/event-streaming/live-events.md). To get an email when a destination starts failing, set up [Notifications](/activate/event-streaming/notifications.md).

## Edit or delete a destination

Open the destination's menu on the **Overview** tab and click **Edit**, **View Connected Streams** or **Delete**. Deleting a destination stops all events to it.


---

# 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/connect-a-destination.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.