> For the complete documentation index, see [llms.txt](https://developer.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.mediarithmics.io/advanced-usages/audiences/audience-segment-feed.md).

# Audience segment feed

An audience feed is a [plugin](/advanced-usages/plugins.md) acting like a connector that allows mediarithmics customers to push their segments to a third-party platform.

It is generic: once a connector to a partner has been created, every customer can use it. Each audience feed has a specific set of options to adapt to each customer.

{% hint style="info" %}
For more details on how to manage consent in segments and feeds, have a look at the [User choice](/advanced-usages/data-privacy-compliance/user-choices.md)s section.
{% endhint %}

## Key concepts

An **audience external feed** is a mediarithmics [plugin](/advanced-usages/plugins.md) specific to a partner, but shared across customers. In the UI, it is called Server-side plugin: go to a specific segment, click **Add a feed,** and you will see a feed type called server-side. It is marketed as connectors or server-to-server connectors.

It has:

* Plugin definition
  * group\_id: `com.mediarithmics.audience.externalfeed`
  * artifact\_id: `[[partner]]-connector`&#x20;
* Plugin versions with
  * Deployed code
  * An external service referencing partner’s API&#x20;
  * Configuration files for things like credentials, tokens, technical configurations

A **feed** is an instance of an audience feed. It is specific to a segment in an organisation. It has:

* Feed ID
* Instance properties specified by users in the UI when adding a feed to a segment.

A **feed session** is initiated whenever an external feed is activated. A new session will also be created if a feed is paused and then reactivated. This session is not visible in the UI.

A **feed preset** is a template allowing users to easily create feed instances with pre-configured properties. You can, for example, create a Facebook feed preset containing your key for your organisation, and you won't have to remember it every time you set up a new feed.


---

# 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://developer.mediarithmics.io/advanced-usages/audiences/audience-segment-feed.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.
