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

# Beeswax

Push audiences to the Beeswax DSP to run display and video campaigns.

The Beeswax connector pushes your audiences to the Beeswax Demand Side Platform, so you can run media campaigns - display, video and the rest.

<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>Cookies, Mobile IDs, Email identifiers, User account IDs</td></tr><tr><td><strong>Authentication</strong></td><td>Buzz Key and connection credentials, shared with your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Run Beeswax media campaigns against an audience built in mediarithmics.
* Split monetisation and own-campaign activity across different advertiser accounts.

### Which identifiers are sent

* **Cookies**
* **Mobile IDs**
* **Email identifiers**
* **User account IDs**

## Connector setup

### Prerequisites

Give your account manager:

1. the **Buzz Key** provided by Beeswax;
2. the Beeswax **connection account** and **connection password**, so the configuration can be set up on the mediarithmics side. Share these two separately, for security;
3. the identifier types you want to push;
4. where relevant, the **advertiser ID** to use. Some customers hold both a global account for monetising audiences and another for running their own campaigns on first-party audiences.

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

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

#### Why should I send the connection account and password separately?

For security. The credentials are configured on the mediarithmics side, and splitting the transmission limits exposure.

#### I have two Beeswax advertiser accounts. Which do I use?

Whichever matches the purpose of this feed. Provide the advertiser ID to your account manager when the audience should go to a specific one.

## Partner documentation

Beeswax documents its own platform at <https://api-docs.freewheel.tv/beeswax/>. 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/beeswax.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.