> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/activate-your-audiences/set-up-a-destination.md).

# Set up a destination

The four-level hierarchy behind every activation - connector, destination, preset, feed - and what you configure at each level.

## Your goal

Get the partner-side plumbing in place once, so that sending an audience to that partner later is a two-minute job rather than a configuration exercise.

## Expected outcome

An authenticated destination for the partner platform, and at least one preset on it, ready to be selected when you create a feed from a segment.

## The four levels

Data activation follows a four-level hierarchy. Configuring the right thing at the right level is what makes activation reusable.

```
Connector  →  Destination  →  Preset  →  Feed
```

<table data-search="false"><thead><tr><th width="150">Level</th><th>What it is</th><th width="200">Who creates it</th></tr></thead><tbody><tr><td><strong>Connector</strong></td><td>A partner platform integration available on the platform - Google DV360, Meta, The Trade Desk.</td><td>mediarithmics</td></tr><tr><td><a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md"><strong>Destination</strong></a></td><td>Your organisation's authenticated connection to a connector. Holds the credentials, and is created once per partner account.</td><td>You, once per partner account</td></tr><tr><td><a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md"><strong>Preset</strong></a></td><td>A reusable configuration on top of a destination: which data is sent, which identifiers are used, how it is formatted.</td><td>You, as many as you have use cases</td></tr><tr><td><a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md"><strong>Feed</strong></a></td><td>The concrete delivery instance. Adds only what is specific to one data stream: the source audience, optional filters, the schedule.</td><td>You, once per segment and use case</td></tr></tbody></table>

{% hint style="info" %}
The point of the hierarchy is that credentials and partner settings are configured **once**, not each time you create a feed. Update a preset and every feed built on it is updated at once.
{% endhint %}

## Where to configure it

Everything at the destination and preset levels lives in **Navigator > Feeds**, which has two tabs:

| Tab               | What it shows                                                                                                                                     |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Overview**      | Every destination and preset in your organisation, with its current authentication status. Filter by connector type or status, or search by name. |
| **Detailed list** | Every feed, with its preset and related segment information. Filter by connector type, destination, preset, status, or name.                      |

Feeds themselves are created from the segment page. See [Send your audience to a destination](/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination.md).

## The order to work in

{% stepper %}
{% step %}

### Check the connector exists

If the partner platform you need is not among the available connectors, it has to be built. See [Requesting a new connector](/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md#requesting-a-new-connector). The catalogue of connectors is the **Connectors** section of this documentation.
{% endstep %}

{% step %}

### Create and authenticate the destination

One per partner account. It must reach the status **Authenticated** before anything can be built on it. See [Destination](/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md).
{% endstep %}

{% step %}

### Create a preset on it

Decide what is sent, and above all **which identifiers** are sent - that decision lives here and cannot be overridden by a feed. See [Preset](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md).
{% endstep %}

{% step %}

### Create feeds from your segments

The feed inherits the preset's configuration, so you only supply what is specific to the stream. See [Feed](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md).
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
Some of this can be restricted by role in your organisation. If you cannot see elements described here, check with your Account manager.
{% endhint %}

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Send your audience to a destination</strong></td><td>Where all of this gets used.</td><td><a href="/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination.md">Send your audience to a destination</a></td></tr><tr><td><strong>Monitor your audiences</strong></td><td>Watching destinations, presets and feeds once they are running.</td><td><a href="/audience-and-activation/activate-your-audiences/monitor-your-audiences.md">Monitor your audiences</a></td></tr></tbody></table>


---

# 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.mediarithmics.io/audience-and-activation/activate-your-audiences/set-up-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.