> 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/preset.md).
# Preset
The reusable configuration every feed inherits: what is sent, which identifiers are used, how it is formatted.
## What a preset is
A **preset** is a reusable configuration attached to a [destination](/audience-and-activation/activate-your-audiences/set-up-a-destination/destination.md). It defines what data is sent to the partner platform, which identifiers are used, and how the data is formatted. Every [feed](/audience-and-activation/activate-your-audiences/set-up-a-destination/feed.md) is built on a preset and inherits its configuration automatically.
Configure shared settings once, reuse them across as many feeds as needed. Update the preset and every feed linked to it is updated at once.
## Create one
Presets are created from within a destination, and the destination must be **Authenticated** first.
{% stepper %}
{% step %}
### Open the destination
Go to **Navigator > Feeds** and open the **Overview** tab. Locate the destination, then click **Add preset** in the menu on the right, or **+ New preset** directly in the main table.
{% endstep %}
{% step %}
### Name and describe it
* **Name** - the label identifying this preset across your organisation.
* **Description** - what this preset does and where it sends data.
{% hint style="info" %}
**Naming that survives contact with a colleague.** Include both the **partner name** and the **product or use case** in the name, and use the description to say when and why the preset should be used. A preset is meant to be picked from a list by someone who did not create it.
{% endhint %}
{% endstep %}
{% step %}
### Set the preset properties
The settings shared by every feed using this preset. They typically include:
* **Account identifiers** - the account, advertiser, or seat ID identifying your organisation at the partner platform.
* **Partner options** - audience type, time to live (TTL), taxonomy, depending on the connector.
* **Field mappings** - how your data is formatted and mapped before being sent.
These are set once, here. Individual feeds do not override them.
{% endstep %}
{% step %}
### Configure the identifying resources
The identifier types sent to the partner to match users. See [Identifying resources](#identifying-resources).
{% endstep %}
{% step %}
### Confirm
Click **Save**. The preset is linked to the parent destination, displayed under it in the Overview tab, and immediately available when creating feeds.
{% endstep %}
{% endstepper %}
## Identifying resources
**Identifying resources** are the types of identifier sent to the partner platform to match users - Email, Mobile Advertising ID, mediarithmics FirstId, and so on. They are configured **at the preset level**, and the available set is determined by what the connector supports.
Feeds linked to the preset use those identifiers automatically and **cannot change them at the feed level**.
{% hint style="info" %}
**Why that constraint is useful.** To stop sending FirstId to a partner, remove it from the preset's identifying resources once. Every feed using that preset is updated immediately - there is no per-feed audit to perform.
{% endhint %}
Which identifiers a given partner accepts is stated on that connector's page in the **Connectors** section, and is shown in the feed's **Identifying resources** section when you configure the preset. The choice you make here is the single biggest lever on [identifier coverage](/audience-and-activation/activate-your-audiences/track-a-feed-stats-and-troubleshoot.md#the-three-numbers-that-matter), and therefore on how much of your segment actually reaches the partner.
## Edit one
{% stepper %}
{% step %}
### Find it
**Navigator > Feeds**, **Overview** tab, under its parent destination. Click **Edit Preset**.
{% endstep %}
{% step %}
### Change what you need
Preset properties or identifying resources.
{% endstep %}
{% step %}
### Review the blast radius
A warning lists the number of affected feeds and their current status - live, stopped, and so on. Review it and confirm.
{% endstep %}
{% endstepper %}
Changes propagate to every feed linked to the preset.
## Delete one
A preset cannot be deleted while any of its linked feeds is active. Either close or archive every feed associated with it first, or use the option to force all the feeds attached to the preset to stop, and delete the preset in the same operation.
To delete: **Navigator > Feeds**, **Overview** tab, find the preset under its destination, click **Delete** and confirm.
{% hint style="danger" %}
Deletion is permanent and cannot be undone. Forcing it also stops every feed attached to the preset.
{% endhint %}
## Presets in automations
An automation's **Feed** node reuses the same presets, and is only visible once you have presets configured. See [Actions](/audience-and-activation/automate/automations-reference/actions.md).
## Related pages
---
# 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/preset.md?ask=&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.