For smooth audience activation, Adform has server-to-server integrations with a range of Activation and Data Management Platforms.
To export data to an external platform, you have to create:
-
Destination Route that determines which account on the external platform you want to export your data to (for example, Advertiser seat on Google side).
-
Destination Rule that allows you to specify which segments to export, set scheduling, and select the Destination Route, where the audiences should be delivered.
Here's the list of all currently available destinations.
Platform name |
Platform type |
Credentials needed |
Comments |
UIDs types available |
---|---|---|---|---|
Active Agent |
DSP |
|
A key name is necessary for the route to export audiences. It's a prefix for each audience that'll be added before each Audience ID in export lines. Otherwise, the audiences won't be assigned correctly during the export. Before exporting the audience from Adform, perform the following steps on Active Agent side:
|
Browser UIDs |
Adobe Audience Manager |
DMP |
DPID Target Data Owner |
Before exporting audiences from Adform DMP to Adobe, you need to create corresponding traits (audiences) in Adobe DMP and specify a trait rule for each of these traits. Trait rules should have the format "ic == trait ID" (where trait ID is Adform Audience ID). If you need any help with trait creation, contact an Adobe Audience Manager representative. Contact DMP Support (audiencebase@adform.com) to create the route. Once the route is created, you can create rules (select audiences to export) as usual. |
Browser UIDs |
|
Social Media |
|
Advertising UIDs |
|
Google Ad Manager (name on Adform platform: Google DDP) |
Ad Server |
|
Google may apply additional fees for data exporting to DoubleClick for Publishers. |
Browser and Advertising UIDs |
Google Display & Video 360 (name on Adform platform: Google DBM) |
DSP |
|
|
Browser UIDS and Advertising IDs |
LiveRamp |
Onboarder |
|
Contact DMP support (audiencebase@adform.com) for support. |
Browser UIDS and Advertising IDs |
Microsoft (formerly Xandr) |
SSP, DSP |
|
ImportantBuyer Member ID has to be unique for every destination route.
|
Browser and Advertising UIDs |
PubMatic |
SSP |
|
Before you prepare your first data export to PubMatic, make sure your PubMatic seat is mapped to Adform. To do so, send an email to emeaaddressability@pubmatic.com, and provide these details:
Other considerations:
|
Browser UIDs |
The Trade Desk |
DSP |
|
|
Browser and Advertising UIDs |
Xaxis Turbine |
DMP |
|
The advertiser name is used to differentiate data exports to Turbine. The value is used as a Destination ID. |
Browser and Advertising UIDs |
Note
Usage reports in Adform are only available for Google Ad Manager (name on Adform platform: Google DDP). For other destinations, it's only available on the destination platform.
Export size reports in Adform are available for all destinations.
External Storage
Browser IDs and Advertising IDs are exported in separate files. The files contain two columns:
-
Cookie ID (Browser Cookie or Advertising ID)
-
Segment ID (Adform Audience ID)
In case any other columns need to be exported, please reach out to DMP support (audiencebase@adform.com).
Platform name |
Platform type |
Credentials needed |
Comments |
UIDs types available |
---|---|---|---|---|
Amazon S3 |
Storage |
|
File Name Prefix is used as a Seat ID |
Browser and Advertising UIDs |
FTP |
Storage |
|
File Name Prefix is used as a Seat ID |
Browser and Advertising UIDs |
SFTP |
Storage |
|
|
Browser and Advertising UIDs |