Skip to main content
This page covers the Adform DMP destination, which sends audience identifiers out of Zeotap CDP to your Adform DMP account, where they arrive as segments you can use for targeting in your programmatic campaigns. Data moves in one direction only: Zeotap CDP does not read data back from Adform. For the separate Adform destination — which is configured with an Adform org type (agency, advertiser or Zeotap) and a category instead of Adform DMP API credentials and a Data provider id — see that page.

What this is

Adform is a media buying platform that enables brands, agencies and publishers to create, buy and sell digital advertising globally. Adform DMP (Data Management Platform) is the data management solution within that platform: it lets businesses collect, organise, analyse and activate large volumes of data drawn from sources such as websites, mobile apps and advertising campaigns. Integrated with Zeotap CDP, the Adform DMP destination uploads audiences directly into your Adform DMP account so you can use them for targeting in your programmatic campaigns. The Adform DMP destination is a batch integration for audiences: you configure it once against an Adform DMP account and then reuse it for every audience you link to it. Neither Adform integration has a source counterpart — both are destinations, so nothing flows from Adform into the CDP.

Supported identifiers

This integration supports MAIDs, Adform Cookies and ID5.

Available actions

The destination exposes a single action, Send identifiers to Adform DMP. It supports ID Extension for expanding an audience before delivery. Adform DMP is not among the integrations where Delete and Delta Upload are enabled.

Prerequisites

Ensure that the following are taken care of before you start this integration.

Adform DMP account

Ensure that you have an Adform DMP account set up. If you do not have an account, contact your Adform Account Manager to set one up.

Adform DMP Account ID

Have your Adform DMP Account ID handy to set up this integration — it is the value you enter as the Data provider id on the destination. If you do not know your Account ID, contact dmp@adform.com.

External platform connection

Ensure that Zeotap CDP is added as an external platform on your Adform DMP account, so that the two can connect. To do this, contact dmp@adform.com with your account details and request that Zeotap CDP be connected as an external platform.

Adform API credentials

You need to register as an OAuth client with the Adform DMP by providing the following details of the client to the Adform support team at dmp@adform.com:
On successful registration, Adform shares the credentials by email to the username you gave them. These are the API Username and API Password you enter on the destination.
You also need an audience to activate, and the destination rights described in the Destinations prerequisites.

Create the Adform DMP destination

1
Log in to the Zeotap CDP app and go to Integrate > Destinations.
2
Click + Create Destination.
The Destinations listing in Zeotap CDP with the Create Destination button highlighted
3
Under All Destinations, search for Adform DMP.
The All Destinations catalogue with the Search for a Destination box highlighted
4
Click Adform DMP. Details about the destination appear on the left of the screen; the fields the integration needs appear on the right. Enter:a. A name for the destination. Choose a name that identifies the Adform DMP account it connects to, so the destination is easy to find when you link an audience.b. The API Username and API Password you obtained from Adform.c. The Data provider id from your Adform DMP account — this is the Account ID you gathered in the prerequisites.
The Enter Destination Details step for Adform DMP, showing the Destination Name, API Username, API Password and Data provider id fields
5
On the mapping screen, choose the action and the identifiers to send:a. Under Choose your Action, select Send identifiers to Adform DMP, then choose the corresponding identifiers under Map the Fields. The output identifiers the platform accepts — MAIDs, Cookies and more — are shown by default. You can edit, add or remove an identifier from the list; see Define the mapping.b. Click Create Destination. The created destination is then listed in the Audiences application, ready to be linked to an audience or segment.
The Mapping step with Send identifiers to Adform DMP chosen under Choose your Action and the Output Identifiers Mapping table under Map the Fields
This integration supports ID Extension for the action Send identifiers to Adform DMP.
For the two entry points into destination configuration and what each part of the configuration does, see Configure a destination. Once the destination is created, link it to the audience you want to activate from the Audiences application — see Link an audience to the destination for the end-to-end workflow. It can take up to three business days for a linked segment to be available at the Adform DMP seat.
The terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an audience or a segment can be a specific group of customers who are over 18 years of age and have performed an addToCart event within the last 30 days.

Verify the audience reached Adform DMP

Confirm delivery from both sides:
  1. In Zeotap CDP — open the destination and review its activity. A successful delivery records a completed run with a non-zero qualified count; a failed run records an error message you can use to diagnose the cause. See Verify the activation worked.
  2. In the Adform console — open Audiences for the account and find the audience delivered from the CDP. It is listed with its audience name, audience ID, audience category and a status, as shown below. Allow up to three business days before expecting it to appear.
The Audiences list in the Adform console showing a delivered audience with an active status, its audience ID, data type and audience category
The two counts will not match exactly — Adform applies its own match-rate filtering to the identifiers it receives — but both should be non-zero.

Troubleshoot the Adform DMP destination

For delivery errors that are not specific to Adform DMP — no customers qualified, a terminated refresh, a rejected payload — see Why deliveries fail and When to contact support.

Next steps

Last modified on November 17, 2026