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

# Send your first-party data to a destination

Create a feed on a segment, then edit, duplicate, resend, or stop it.

## Your goal

Push the users of one of your segments to a partner platform, and keep that stream under control afterwards.

## Expected outcome

A feed attached to the segment, visible on the segment page and in the **Detailed list** tab, moving through its statuses to **Live** and then sending only differences.

## Prerequisites

* An **Authenticated** [destination](/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md) for the partner.
* A [preset](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md) on that destination, carrying the identifying resources you want to send.
* A segment that is populated - persisted and computed, if it is a Query segment.

## Create the feed

Feeds are created from the **segment page**, with the **New feed** button.

{% stepper %}
{% step %}

### Select a preset

The list shows only presets linked to an **Authenticated** destination. Narrow it with:

* **Connector type** - server-side or client-side.
* **Search bar** - by connector name or preset name.
* **Identifying Resources** - by the identifier types configured on the preset.

Each preset card shows the connector name, the parent destination's authentication status, the configured identifying resources, and how many feeds already use that preset.

Select the preset matching your activation goal. The feed inherits all of its configuration.
{% endstep %}

{% step %}

### Configure what is specific to this feed

Only the instance-level settings, such as:

* **Filters** - optional filters refining the audience sent.
* **Target audience specificities** - a taxonomy, a specific audience id, the audience description.
  {% endstep %}

{% step %}

### Review and confirm

A summary shows the selected preset and its key configuration, the parent destination and its authentication status, and the feed-specific settings you just configured. Confirm to create the feed.
{% endstep %}
{% endstepper %}

The feed appears in the **Detailed list** tab and on the segment page.

## What the feed inherits, and what it does not

{% columns %}
{% column %}

### Inherited from the preset

* Partner account identifiers.
* Audience type, TTL, and other partner-side options.
* Field mappings.
* Identifying resources.

Visible on the feed, **read-only** there. To change any of them, update the [preset](/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md) - changes propagate to every feed using it.
{% endcolumn %}

{% column %}

### Fixed at creation

* **Source segment.** Set at creation and cannot be changed.
* **Run schedule.** All feeds run on a daily schedule.
  {% endcolumn %}
  {% endcolumns %}

## Reading the feed card on a segment

The segment page lists the feeds hooked to it. Each card shows:

* **The feed name.**
* **The feed type** - the connector it uses.
* **The feed status** - for example "Sending updates when users enter or leave".
* **The number of identifiers, or users, pushed and removed** through the feed in the last 24 hours, where applicable.

## Manage a running feed

A feed is reached either from **Navigator > Feeds**, **Detailed list** tab, or from the segment page by opening the feed menu and selecting **Configuration** or **Stats**.

<table data-search="false"><thead><tr><th width="180">Action</th><th>What it does, and the constraint</th></tr></thead><tbody><tr><td><strong>Edit</strong></td><td>Change the feed name and the properties specific to this feed. A client-side feed can only be edited while it is <strong>not active</strong> - stop it first if it is live or syncing.</td></tr><tr><td><strong>Duplicate</strong></td><td>Adds another feed on the segment reusing an existing feed's configuration. The configuration is copied and remains editable.</td></tr><tr><td><strong>Resend all users</strong></td><td>Available when the feed is <code>LIVE</code>. Reboots the connection with the destination partner, then resends every user in the segment.</td></tr><tr><td><strong>Delete</strong></td><td>The feed must be <strong>stopped</strong> first. Deletion is permanent - if you may need the stream again, archive rather than delete.</td></tr></tbody></table>

{% hint style="info" %}
**Resend all users** is the right tool after a partner-side problem, and the wrong tool after a segment edit: an edited segment already reconciles itself through upserts and deletes at the next computation, without a full resend. See [What a Live feed sends](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md#what-a-live-feed-sends).
{% endhint %}

## Verification

* The feed reaches **Live** after initial loading. The seven server-side statuses are listed in [Feed](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md#server-side-feeds).
* Upserts appear in the feed's stats, and the percentage of users for which compatible identifiers could be sent is acceptable. See [Track a feed](/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md).
* The audience is visible at the partner. For a client-side feed, expect a ramp-up rather than an immediate figure.

## Troubleshooting

<table data-search="false"><thead><tr><th width="300">Symptom</th><th>Where to look</th></tr></thead><tbody><tr><td>You cannot create the feed - no preset in the list</td><td>The destination is not <strong>Authenticated</strong>, or no preset exists on it. See <a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md#understand-destination-status">Understand destination status</a>.</td></tr><tr><td>The feed is created but sends nothing</td><td>The segment is not persisted or not yet computed.</td></tr><tr><td>Far fewer users at the partner than in the segment</td><td>Identifier coverage. See <a href="/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md#the-three-numbers-that-matter">The three numbers that matter</a>.</td></tr><tr><td>You want to change the identifiers sent</td><td>Not editable on the feed. Update the <a href="/audience-and-activation/activate-your-audiences/set-up-a-destination/preset.md#identifying-resources">preset</a>.</td></tr><tr><td>Users you removed from the segment are still targeted at the partner</td><td>Expected on a client-side feed - there is no exit signal. Use an exclusion segment in the partner's campaign configuration.</td></tr></tbody></table>

## 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>Monitor your audiences</strong></td><td>Watching every feed in the organisation at once.</td><td><a href="/audience-and-activation/activate-your-audiences/monitor-your-audiences.md">Monitor your audiences</a></td></tr><tr><td><strong>Export segment identifiers</strong></td><td>The manual alternative to a feed.</td><td><a href="/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities/export-segment-identifiers.md">Export segment identifiers</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/send-your-first-party-data-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.