> 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.md).

# FreeWheel

The four FreeWheel connectors, each reaching a different FreeWheel product.

FreeWheel is reached four different ways, and unlike most vendors the choice is not a mechanism preference - **each connector targets a different FreeWheel product**. Picking the wrong one sends your audience somewhere it cannot be used.

## Which connector to use

<table data-search="false"><thead><tr><th width="300">Connector</th><th width="220">Reaches</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/freewheel/audience-manager.md"><strong>Audience Manager</strong></a></td><td>FreeWheel Audience Manager</td><td>Two-file ingestion - a Segment Taxonomy file and a Segment Membership file - uploaded to a FreeWheel-managed S3 bucket. Introduced to replace the deprecated AIC system.</td></tr><tr><td><a href="/connectors/destinations/freewheel/external-feed.md"><strong>External Feed</strong></a></td><td>FreeWheel SFX</td><td>Server-to-server.</td></tr><tr><td><a href="/connectors/destinations/freewheel/file-sharing.md"><strong>File Sharing</strong></a></td><td>FreeWheel MRM</td><td>Over FreeWheel's SFTP. Requires mediarithmics to be registered as a Data Provider in your FreeWheel account, which FreeWheel does, not us.</td></tr><tr><td><a href="/connectors/destinations/freewheel/pixel.md"><strong>Pixel</strong></a></td><td>A FreeWheel remarketing account</td><td>Client-side. Fires your FreeWheel pixel from the browser; mediarithmics sends no identifiers.</td></tr></tbody></table>

## What each connector sends

<table data-search="false"><thead><tr><th width="230">Connector</th><th width="180">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/freewheel/audience-manager.md">Audience Manager</a></td><td>Server-side</td><td>Cookies, TV IDs, Mobile IDs, IP addresses</td></tr><tr><td><a href="/connectors/destinations/freewheel/external-feed.md">External Feed</a></td><td>Server-side</td><td>Cookies, Mobile IDs</td></tr><tr><td><a href="/connectors/destinations/freewheel/file-sharing.md">File Sharing</a></td><td>Server-side</td><td>Cookies, User account IDs</td></tr><tr><td><a href="/connectors/destinations/freewheel/pixel.md">Pixel</a></td><td>Client-side (pixel)</td><td>None</td></tr></tbody></table>

{% hint style="warning" %}
The Audience Manager connector applies a **90-day TTL** to every user–segment association. FreeWheel removes the association automatically after that unless it is refreshed; mediarithmics resends within the window, based on valid user consent.
{% endhint %}

Cookie-based identifiers require cookie matching activated on the FreeWheel side. Ask your FreeWheel account manager.

## 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.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.