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

# AdsWizz

Send audiences to AdsWizz to target them across podcasts, music streaming and digital radio.

The AdsWizz connector sends your audiences to AdsWizz, so a segment built in mediarithmics can be targeted across audio environments: podcasts, music streaming platforms and digital radio.

<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>AdsWizz Listener IDs (third-party cookies), Mobile IDs (IDFA / AAID), IP addresses (IPv4 and IPv6)</td></tr><tr><td><strong>Authentication</strong></td><td>AdsWizz S3 credentials and encryption settings</td></tr></tbody></table>

{% hint style="info" %}
Setting up this connection involves work on the mediarithmics side. Contact your account manager to get the AdsWizz connection and cookie sync set up.
{% endhint %}

## Description

### What is AdsWizz?

AdsWizz is an advertising technology platform specialised in digital audio. It delivers targeted ads across streaming services, podcasts and online radio.

With AdsWizz, you can:

* Activate audiences across audio inventory at scale.
* Deliver personalised and programmatic audio ads.
* Use deterministic and probabilistic identifiers for targeting.
* Measure and optimise campaign performance across devices.

### What you can do with this connector

* Enrich AdsWizz campaigns with your first-party data.
* Improve targeting, personalisation and campaign performance on audio inventory.

### Which identifiers are sent

* **AdsWizz Listener IDs** - third-party cookies. Sending these requires cookie sync.
* **Mobile advertising IDs** - IDFA and AAID.
* **IP addresses** - IPv4 and IPv6.

## Connector setup

### Prerequisites

* An **AdsWizz account**.
* Access to an **AdsWizz S3 bucket**, provided by AdsWizz.
* Access to the mediarithmics platform.

### Authentication

The S3 credentials and encryption settings come from AdsWizz and are configured on the mediarithmics side. You do not enter them on the feed yourself.

### Setup steps

{% stepper %}
{% step %}
**Select the AdsWizz connector.**
{% endstep %}

{% step %}
**Fill in the required configuration.**

<table data-search="false"><thead><tr><th width="260">Field</th><th></th></tr></thead><tbody><tr><td><strong>File destination token</strong></td><td>Defines which file destination is used to send the identifier files. Provided by your account manager.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Select the identifying resources to activate.**

To send third-party cookies, select `MUM_ID`.
{% 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

* **Segments are declared in a taxonomy file.** Once declared, users are added to and removed from the corresponding AdsWizz audiences automatically.
* **Cookie sync is optional.** It is only needed to retrieve AdsWizz Listener IDs, and therefore only to send third-party cookies. Mobile advertising IDs and IP addresses do not depend on it.

## FAQ

#### How are segments shared with AdsWizz?

Segments are declared in a taxonomy file. Users are then added or removed in the matching AdsWizz audiences automatically.

#### Do I need cookie sync?

Only to send AdsWizz Listener IDs, which are third-party cookies. If you activate on mobile advertising IDs or IP addresses, you do not.

#### Is this connector self-service?

Partly. Creating feeds is self-service once the connection exists, but the initial setup and the cookie sync are arranged with your account manager.

## Partner documentation

`TODO` - AdsWizz publishes no public product documentation; its MyAdsWizz knowledge base requires a partner login. Ask your mediarithmics account manager for the partner-side setup guide.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>DSP</strong></td><td>What a DSP needs from your CDP, and every mediarithmics connector that reaches one.</td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td><strong>Getting started</strong></td><td>Every documented connector, by partner type and by name.</td><td><a href="/connectors/readme.md">Getting started</a></td></tr></tbody></table>


---

# 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/adswizz.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.