> 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/send-your-audience-to-a-destination.md).

# Send your audience to a destination

Send a segment to a partner platform, and decide which identifiers carry it there.

## Your goal

Get the users of a segment into a partner platform, so a campaign can act on them.

## Expected outcome

A feed on the segment, running against an authenticated destination, sending upserts and deletes as the segment changes - and enough identifier coverage for the audience to be worth activating.

## Before you start

Feeds sit at the bottom of the activation hierarchy, so two things must exist already:

* A **destination** for the target partner, with the status **Authenticated**.
* A **preset** on that destination, configured with the identifying resources you want to send.

If either is missing, start with [Set up a destination](/audience-and-activation/activate-your-audiences/set-up-a-destination.md).

The segment must also be ready: for a [Query segment](/audience-and-activation/build-your-audiences/segment-reference/segment-types/query-segment.md), that means **persisted and computed**, not merely counted. See [Counting is not persistence](/audience-and-activation/build-your-audiences/segment-reference.md#counting-is-not-persistence).

## Two jobs, one mechanism

<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 first-party data to a destination</strong></td><td>The standard job: create the feed on a segment, then manage it - edit, duplicate, resend, stop.</td><td><a href="/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination/send-your-first-party-data-to-a-destination.md">Send your first-party data to a destination</a></td></tr><tr><td><strong>Extend your reach with third-party ids (Connect ID)</strong></td><td>When your own identifiers do not reach far enough, and third-party identifiers have to carry the audience.</td><td><a href="/audience-and-activation/activate-your-audiences/send-your-audience-to-a-destination/extend-your-reach-with-third-party-ids-connect-id.md">Extend your reach with third-party ids (Connect ID)</a></td></tr></tbody></table>

Both go through the same object - a [feed](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md) on a [preset](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md). What differs is which identifying resources the preset carries, and therefore how much of your segment the partner can act on.

## What decides how many users arrive

Three things, in this order:

1. **The segment's population.** Only what the segment actually holds can be sent. See [Check your audience reach and stats](/audience-and-activation/analyze-your-data/check-your-audience-reach-and-stats.md).
2. **The identifiers the preset sends.** An identifier your users rarely carry produces a small audience at the partner, however large the segment. See [Identifying resources](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md#identifying-resources).
3. **The feed type.** A client-side feed can only synchronise users while they are visiting your sites, so it ramps up rather than landing at once. See [Client-side feeds](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md#client-side-feeds).

{% hint style="info" %}
When an activation underperforms, check them in that order. Most "the feed is broken" reports turn out to be point 2 - see [The three numbers that matter](/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md#the-three-numbers-that-matter).
{% 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>Feed</strong></td><td>The two feed types, their statuses, and what a live feed sends.</td><td><a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md">Feed</a></td></tr><tr><td><strong>Track a feed (stats and troubleshoot)</strong></td><td>Reading a running feed's numbers.</td><td><a href="/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md">Track a feed (stats and troubleshoot)</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/send-your-audience-to-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.