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

# Pubmatic

Share segments with Pubmatic to monetise your inventory across ad exchanges.

The Pubmatic connector shares your segments with Pubmatic, so you can sell your ad inventory to advertisers across different ad exchanges and raise your ad revenue.

<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>Mobile IDs, ID5 IDs</td></tr><tr><td><strong>Authentication</strong></td><td>Pubmatic Account ID shared with your account manager</td></tr></tbody></table>

## Description

### What is Pubmatic?

Pubmatic is a sell-side platform. mediarithmics is registered with it as a **Data Provider**, which is what allows your segments to be linked to your Pubmatic account.

### What you can do with this connector

* Generate a Pubmatic audience from a mediarithmics segment.
* Share that audience from your main Pubmatic account to an additional one.

### Which identifiers are sent

* **Mobile IDs**
* **ID5 IDs**

## Connector setup

### Prerequisites

* A Pubmatic account, and its **Account ID**. Give the Account ID to your mediarithmics account manager - it is what links your account to mediarithmics inside Pubmatic.

### Setup steps

{% stepper %}
{% step %}
**Send your Pubmatic Account ID to your mediarithmics account manager.**
{% endstep %}

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

<table data-search="false"><thead><tr><th width="300">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>A name you choose.</td></tr><tr><td><strong>Main Pubmatic Account ID</strong></td><td>The account where the audience is generated and identifiers are pushed.</td></tr><tr><td><strong>Country Code</strong></td><td>A 2 or 3 letter country code. Required by Pubmatic.</td></tr><tr><td><strong>Shared Pubmatic Account ID</strong></td><td>An additional account the audience is shared to, from the main one.</td></tr><tr><td><strong>Pubmatic Segment ID</strong></td><td>Filled in by the connector when the segment is created. You do not set it.</td></tr><tr><td><strong>Segment Name</strong></td><td>A custom name for the generated Pubmatic audience. Left empty, the mediarithmics segment name is used.</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

#### Do I have to fill in the Pubmatic Segment ID?

No. The connector fills it in itself when the segment is created on the Pubmatic side.

#### Can I share the audience with a second Pubmatic account?

Yes, through **Shared Pubmatic Account ID**. The audience is generated on the main account and shared from there.

## Partner documentation

PubMatic documents its own platform at <https://help.pubmatic.com/>. 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/pubmatic.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.