> 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/connectors/destinations/freewheel/audience-manager.md).

# Audience Manager

Share audiences with FreeWheel Audience Manager through its two-file S3 ingestion.

The FreeWheel Audience Manager connector shares your audiences with FreeWheel's Audience Manager.

{% hint style="info" %}
This connector was introduced to support audience activation following the deprecation of the legacy AIC system.
{% endhint %}

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/ssp-and-ad-servers.md">SSP &#x26; ad servers</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Cookies, TV IDs, Mobile IDs, IP addresses</td></tr><tr><td><strong>Authentication</strong></td><td>Base configuration set up by your account manager</td></tr></tbody></table>

## Description

### How FreeWheel Audience Manager works

Audience Manager ingests segments through a **two-file system**. Both files are uploaded to a dedicated S3 bucket managed by FreeWheel:

<table data-search="false"><thead><tr><th width="260">File</th><th></th></tr></thead><tbody><tr><td><strong>Segment Taxonomy file</strong></td><td>Defines the segments to create or update, with metadata: segment ID, name, category, description.</td></tr><tr><td><strong>Segment Membership file</strong></td><td>The list of user identifiers belonging to each segment.</td></tr></tbody></table>

{% hint style="warning" %}
**A separate membership file is generated and uploaded per identifier type** - one for IDFA, one for AAID, and so on.
{% endhint %}

### Which identifiers are sent

* **Cookies**
* **TV IDs**
* **Mobile IDs**
* **IP addresses**

{% hint style="info" %}
**Custom identifiers.** mediarithmics can handle custom identifier types where a platform integration or business case requires it. Contact your account manager first - they set up the configuration for creation and activation. Custom identifiers must also be approved and set up in FreeWheel so they can be ingested.
{% endhint %}

FreeWheel is reached by several connectors and they behave differently - [the comparison is on the FreeWheel page](/connectors/destinations/freewheel.md).

## Connector setup

### Prerequisites

{% hint style="warning" %}
**Contact your account manager before the initial setup** so the base configuration can be created.
{% endhint %}

* Your **MRM Network ID**.
* For cookie-based identifiers, **cookie matching activated on the FreeWheel side** - ask your FreeWheel account manager.

### Setup steps

{% stepper %}
{% step %}
**Ask your mediarithmics account manager to create the base configuration.**
{% endstep %}

{% step %}
**Select the FreeWheel Audience Manager connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="260">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The name of the feed as it appears in the platform.</td></tr><tr><td><strong>MRM Network ID</strong></td><td>The FreeWheel network identifier the data must be pushed to.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier types to synchronise through this feed.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

### Ingestion time

* The **Segment Taxonomy file** is processed **within 1 hour** of being sent. The segments then become available in FreeWheel.
* The **Segment Membership file** is ingested **within the same day**. No exact time is guaranteed - it depends on the size and number of files, and there is one file per identifier type.

### Time to live

Each user–segment association has a **maximum TTL of 90 days**. After that, FreeWheel removes the association automatically unless it has been refreshed.

{% hint style="info" %}
mediarithmics resends user–segment associations within the TTL window, based on valid user consent, so qualified users stay active without interruption.
{% endhint %}

### Geographic segments

FreeWheel offers geographic targeting, which lets you share geographic data held in the datamart - postal codes, regions, countries - to build segments. Activating it requires your account manager; contact them and follow the procedure they describe.

### Automatic audience definitions

You can enable, at preset level, the automatic creation of one audience definition in FreeWheel Audience Manager per segment shared with FreeWheel. Ask your account manager to enable it. Presets are covered in the **Audience & Activation** section, under *Activate your audiences › Set up a destination › Preset*.

{% hint style="warning" %}
Following CNIL guidance on cookies and trackers, make sure that:

1. the partner is explicitly named when you collect user consent for targeting purposes, or the equivalent;
2. the partner is listed in your cookie policy - they may drop a cookie on your users' browsers from your websites.
   {% endhint %}

## FAQ

#### Why do my users disappear from FreeWheel after a while?

The user–segment association has a 90-day TTL on the FreeWheel side. mediarithmics resends associations within that window based on valid user consent, so a user whose consent is no longer valid will not be refreshed.

#### Why is one file per identifier type generated?

Because FreeWheel's ingestion requires it. That is also why membership ingestion time varies - it depends on the number and size of the files.

#### When will my segment appear in FreeWheel?

The taxonomy file is processed within an hour, so the segment shell appears quickly. Membership follows within the same day.

## Partner documentation

FreeWheel documents its own platform at <https://api-docs.freewheel.tv/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# 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/connectors/destinations/freewheel/audience-manager.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.