Export Audiences to Third-Party Activation Platforms

Greta
Greta
  • Updated

For smooth audience activation, Adform has server-to-server integrations with a range of Activation and Data Management Platforms.

Before exporting audience data to third-party platforms, clients should ensure that they have the necessary contractual rights and that the export is supported by the applicable legal basis and required privacy signals. Clients remain responsible for ensuring that recipient platforms are authorized to receive and process the exported data.

To export data to an external platform, you have to create:

  1. Destination Route that determines which account on the external platform you want to export your data to (for example, Advertiser seat on the Google side).

  2. Destination Rule that allows you to specify which segments to export, set the schedule, and select the Destination Route, where the audiences should be delivered.

Here's a table of all available destinations:

Platform name

Platform type

Credentials needed

Comments

UIDs types available

Active Agent

DSP

  • File Name Prefix — used as Seat ID

  • Key

A key name is necessary  for the route to export audiences. It acts as  a prefix for each audience that is 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:

  1. Create an attribute. It's a key that needs to be entered in Adform's Route (Destinations) later.

  2. Create audiences under the attribute. The audiences should have the same IDs as in Adform.

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 an Adform Audience ID). 

If you need help with trait creation, contact an Adobe Audience Manager representative.  

Contact DMP Support (dmp@adform.com) to create the route.  After you have created the route, you can create rules (select audiences to export) as usual.

Browser UIDs

Facebook

Social Media

  • Advertiser Account ID

  • Access Token

See Prepare for Audience Export to Facebook article for more information.

Advertising UIDs

Google Ad Manager (name on Adform platform: Google DDP)

Ad Server

  • Entity ID

  • Product Type

  • Bid Manager for Partner

  • Bid Manager for Advertiser

  • DoubleClick for Publishers

  • Licenses Currency

  • The main goal of data sharing is data selling.

  • Entity ID is used as a Seat ID.

  • License Currency is a case-sensitive value, and must be written in upper case (for example, EUR, TRY, USD).

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

  • Entity ID

  • Product Type

  • Bid Manager for Partner

  • Bid Manager for Advertiser

  • DoubleClick for Publishers

  • The main goal of data sharing is customer’s first-party data sharing for campaigns running across DV360 platform.

  • Adform (823-340-6557) must be allow listed for your DV360 account. To do that, reach out to your Google representative.

Browser UIDS and Advertising IDs

LiveRamp

Onboarder

  • SFTP Username

  • SFTP Password

Contact DMP support (dmp@adform.com) for support.

Browser UIDS and Advertising IDs

Microsoft (formerly Xandr)

SSP, DSP

  • Buyer ID

  • Member ID

Important

Buyer Member ID must be unique for every destination route.

  • Buyer Member ID is used as Seat ID.

  • To activate data sharing, submit a ticket to Microsoft support.

Browser and Advertising UIDs

PubMatic

SSP

  • Data Provider ID

  • Account ID

  • Account type (indicate Publisher or Buyer type)

Before you prepare your first data export to PubMatic, make sure your PubMatic seat is mapped to Adform. Do this by sending an email to emeaaddressability@pubmatic.com, and provide the following details:

  1. Adform API credentials: dmp.integrations@adform.com

  2. PubMatic Account ID

  3. PubMatic Data Provider ID

Other considerations:

  • Entity ID is used as a Seat ID

  • The selected account type will reflect the settings on the PubMatic side.

Browser UIDs

The Trade Desk

DSP

  • Advertiser ID

  • Secret Key

  • Advertiser ID is used as Seat ID.

  • The export allows sharing customers' first-party data for campaigns running on TTD.

Browser and Advertising UIDs

Xaxis Turbine

DMP

  • Region

  • Advertiser name

The advertiser's 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 (called Google DDP in the Adform platform). 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 (dmp@adform.com).

Platform name

Platform type

Credentials needed

Comments

UIDs types available

Amazon S3

Storage

  • Region

  • Bucket

  • Folder

  • File Name Prefix

  • Access Key

  • Secret Key

  • Trigger File Name

File Name Prefix is used as a Seat ID

Browser and Advertising UIDs

FTP

Storage

  • Host

  • Folder

  • File Name Prefix

  • User

  • Password

File Name Prefix is used as a Seat ID

Browser and Advertising UIDs

SFTP

Storage

  • Host

  • Folder

  • File Name Prefix

  • User

  • Password

  • Key

  • File Name Prefix is used as a Seat ID.

  • Either a password or key is required to fill in.

Browser and Advertising UIDs

Was this article helpful?

/
How we can make it better?

Thank you for your feedback!