> 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/file-sharing.md).

# File Sharing

Share audiences with FreeWheel MRM over their SFTP.

The FreeWheel File Sharing connector shares your audience with **FreeWheel MRM** (Monetization Rights Management), using their SFTP.

<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, User account IDs</td></tr><tr><td><strong>Authentication</strong></td><td>mediarithmics registered as a Data Provider in your FreeWheel account</td></tr></tbody></table>

## Description

### What you can do with this connector

* Deliver a mediarithmics segment into FreeWheel MRM over SFTP.

### Which identifiers are sent

* **Cookies**
* **User account IDs**

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

## Connector setup

### Prerequisites

* **mediarithmics configured as a Data Provider in your FreeWheel account.** This is done by your FreeWheel account team - reach out to them directly. Without it, your segment cannot be received.
* Your **MRM Network ID**.
* If you intend to send cookies, **cookie matching activated on your organisation** - confirm with your account manager.

### Authentication

Your mediarithmics account manager provides the **Credentials name** the feed references.

### Setup steps

{% stepper %}
{% step %}
**Ask your FreeWheel account team to register mediarithmics as a Data Provider.**
{% endstep %}

{% step %}
**Select the FreeWheel File Sharing connector under server-side feeds.**
{% endstep %}

{% step %}
**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 displayed in the platform.</td></tr><tr><td><strong>MRM Network ID</strong></td><td>Your FreeWheel network ID, so the data lands in the right place.</td></tr><tr><td><strong>Credentials name</strong></td><td>Provided by your mediarithmics account manager.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier types to send to FreeWheel.</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

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

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

## FAQ

#### Nothing arrives in FreeWheel. What should I check first?

Whether mediarithmics is registered as a Data Provider on your FreeWheel account. That step is done by FreeWheel, not by mediarithmics, and it is the usual cause.

#### I want to send my audience to FreeWheel SFX, not MRM. Which connector?

[FreeWheel - External Feed](/connectors/destinations/freewheel/external-feed.md).

## 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/file-sharing.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.