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

# AdForm

Share audiences with the AdForm DSP, with a taxonomy definition and separate file destinations per identifier.

The AdForm Audience Feed connector shares your audience with the AdForm DSP.

<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, third-party cookies (AdForm cookies)</td></tr><tr><td><strong>Authentication</strong></td><td>File destination tokens and taxonomy credentials from your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Send a mediarithmics segment to the AdForm DSP.
* Place the audience inside an AdForm taxonomy of your choosing.
* Deliver cookies and mobile IDs to separate destinations.

### Which identifiers are sent

* **Mobile IDs**
* **Third-party cookies** - AdForm cookies

{% hint style="warning" %}
To send third-party cookies, contact your account manager to activate the **server-side cookie sync**.
{% endhint %}

{% hint style="info" %}
A client-side cookie sync with AdForm is in progress. It will need to be set up on your tracked websites.
{% endhint %}

## Connector setup

### Prerequisites

Ask your mediarithmics account manager for:

* the **file destination token for cookies**, if you are sharing cookies;
* the **file destination token for mobiles**;
* the **taxonomy credentials** used to upload the taxonomy.

### Setup steps

{% stepper %}
{% step %}
**Select the AdForm Audience Feed under server-side feeds.**
{% endstep %}

{% step %}
**Fill in the target destination.**

<table data-search="false"><thead><tr><th width="320">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>Identifiers resources</strong></td><td>The identifiers to synchronise through this feed.</td></tr><tr><td><strong>File destination token for Cookies</strong></td><td>Required to share cookies. Ask your account manager.</td></tr><tr><td><strong>File destination token for Mobiles</strong></td><td>Ask your account manager.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Fill in the taxonomy definition.**

<table data-search="false"><thead><tr><th width="320">Field</th><th></th></tr></thead><tbody><tr><td><strong>Taxonomy credentials</strong></td><td>The credentials name used to upload the taxonomy. Provided by your mediarithmics account manager.</td></tr><tr><td><strong>Segment Category</strong></td><td>The categories the audience is stored in, separated by slashes (<code>/</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*.

## FAQ

#### Why are my cookies not being sent?

The server-side cookie sync has to be activated by your account manager, and the cookie file destination token must be filled in.

#### Why are there two file destination tokens?

Cookies and mobile IDs are delivered separately, each to its own destination.

## Partner documentation

Adform documents its own platform at <https://www.adformhelp.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/adform.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.