> 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/magnite-ex-rubicon.md).

# Magnite (ex Rubicon)

Share audiences with the Magnite ad exchange.

The Magnite connector shares your audiences with the Magnite ad exchange.

<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</td></tr><tr><td><strong>Authentication</strong></td><td>Publisher and partner IDs shared with your account manager</td></tr></tbody></table>

## Description

### What is Magnite?

Magnite, formerly Rubicon, operates an ad exchange. Audiences arriving from mediarithmics become Magnite audiences.

### What you can do with this connector

* Make a mediarithmics segment targetable in Magnite.
* Feed an existing Magnite audience instead of creating a new one.

### Which identifiers are sent

* **Cookies**

## Connector setup

### Prerequisites

Give your account manager:

* your **publisherId** - for example `16298`;
* your **partnerId** - for example `37792`.

### Authentication

Your account management team returns a **Credential Name**, which links the feed to the credentials you supplied. The IDs themselves are not entered on the feed.

### Setup steps

{% stepper %}
{% step %}
**Send your publisherId and partnerId to your account manager.**
{% endstep %}

{% step %}
**Select the Magnite connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="280">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>Credential Name</strong></td><td>Provided by your mediarithmics account management team.</td></tr><tr><td><strong>Target Magnite Audience Id</strong> <em>(optional)</em></td><td>The ID of an existing Magnite audience to feed, instead of creating a new one.</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*.

## FAQ

#### Can I feed a Magnite audience that already exists?

Yes. Put its ID in **Target Magnite Audience Id** and the feed will not create a new one.

## Partner documentation

Magnite documents its own platform at <https://help.magnite.com/help>. 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/magnite-ex-rubicon.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.