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

# Yahoo Advertising

Push audiences to the Yahoo DSP to run media campaigns.

The Yahoo connector pushes your audiences to the Yahoo Demand Side Platform, so you can run media campaigns against them.

<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/dsp.md">DSP</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Mobile IDs, Emails (SHA-256), Cookies</td></tr><tr><td><strong>Authentication</strong></td><td>MDM ID shared with your mediarithmics contact</td></tr></tbody></table>

## Description

### What you can do with this connector

* Run Yahoo media campaigns against an audience built in mediarithmics.
* Push to a Yahoo audience that already exists.
* Control how long a user stays associated with the audience.

### Which identifiers are sent

* **Mobile IDs**
* **Emails** - SHA-256
* **Cookies**

## Connector setup

### Prerequisites

* Your **MDM ID**, available in the Yahoo DSP portal. Give it to your mediarithmics point of contact.

{% hint style="warning" %}
Cookie matching must be activated on your organisation. Contact your account manager to confirm.
{% endhint %}

### Authentication

Once your account manager has the MDM ID, they complete the configuration and return a **Credentials name** for the feed to reference.

### Setup steps

{% stepper %}
{% step %}
**Send your MDM ID to your mediarithmics point of contact.**
{% endstep %}

{% step %}
**Select the Yahoo 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>Identifies the feed within the platform.</td></tr><tr><td><strong>Segment type</strong></td><td><code>custom</code>, <code>syndicated</code> or <code>private</code>.</td></tr><tr><td><strong>Identifier to send</strong></td><td>The identifier types to send. SHA-256 emails and MAIDs are available - for example <code>EMAIL,MOBILE_AND,MOBILE_IOS</code>.</td></tr><tr><td><strong>Credentials name</strong></td><td>Provided by your account manager.</td></tr><tr><td><strong>Identifiers resources</strong></td><td>The identifier types to send to Yahoo.</td></tr><tr><td><strong>Yahoo audience name</strong></td><td>The name of the audience generated in Yahoo.</td></tr><tr><td><strong>Yahoo audience id</strong></td><td>An existing Yahoo audience to push to.</td></tr><tr><td><strong>TTL (User Life Span)</strong></td><td>How many days a user stays associated with the audience. Default <code>90</code>.</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

#### Where do I find my MDM ID?

In the Yahoo DSP portal.

#### How long do users stay in the Yahoo audience?

For the number of days set in **TTL (User Life Span)**. The default is 90.

## Partner documentation

Yahoo DSP documents its own platform at <https://help.yahooinc.com/dsp-api/docs/dsp-api-help-home>. 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/yahoo-advertising.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.