Export Audiences to Third-Party Activation Platforms

Toma
Toma
  • Updated

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:

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

  2. 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

  • File Name Prefix — used as Seat ID

  • Key

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:

  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 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

Amazon DSP

DSP

  • Advertiser ID

  • Country

  • Advertiser ID is used as Seat ID.

  • Country is provided by Amazon DSP for data import to their system.

Browser UIDs

Facebook

Social Media

  • Advertiser Account ID

  • Access Token

Read more

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

  • DoubleClick Ad Exchange

  • 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, therefore, should be indicated in upper case (for example, EUR, TRY, USD).

Browser and Advertising UIDs

Google Ads (name on Adform platform: Adwords.  YouTube and Google Display Network) 

Search

Entity ID

  • The main goal of the data sharing is to use customer’s first-party data within Google Ads.

  • This destination isn't active for new customers. Only available for accounts created before April 1st, 2019.

  • Entity ID is used as Seat ID.

  • Audience information for users can be passed to Google Ads via Adform Audience Tag.

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

  • DoubleClick for Exchange

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

  • Adform (823-340-6557) has to be whitelisted 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 (audiencebase@adform.com) for support.

Browser UIDS and Advertising IDs

MediaMath

DSP

File Name Prefix

  • File name prefix is used as Seat ID.

  • Allows selling data in MediaMath, the price has to be applied on MediaMath side

  • To export successfully, the audience must match on both sides. Create the same audience on MediaMath as you have on Adform DMP. Please contact MediaMath support to make sure that the audiences are matched properly.

  • You can provide Adform taxonomy to MediaMath to map Adform Audience IDs with Adform audience name (on MediaMath side) easier.

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. To do so, send an email to emeaaddressability@pubmatic.com, and provide these 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 and Advertising UIDs

Magnite (name on Adform platform: Rubicon)

SSP

Partner ID

  • Partner ID is used as a Seat ID.

  • Adform needs to be whitelisted on Magnite.

  • You have to create audiences on Magnite with the same IDs as these audiences have in Adform to perform the export correctly.

Browser UIDs

The Trade Desk

DSP

  • Advertiser ID

  • Secret Key

  • Advertiser ID is used as Seat ID.

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

Browser and Advertising UIDs

Xandr (AppNexus)

SSP, DSP

  • Buyer ID

  • Member ID

  • Buyer Member ID is used as Seat ID.

  • To activate data sharing, you have to submit a ticket for Xandr support.

Browser and Advertising UIDs

Xaxis Turbine

DMP

  • Region

  • Advertiser name

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) and MediaMath. 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

  • 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!