• All
  • Country
  • Product
Save as pdf

General Guidelines

Adform DMP collects data from a number of sources: Ad campaigns, mobile, CRM, offline, website content, other DSP or DMP platforms. All this data is keyed off the global Adform User ID. In order to sync and correlate the data with some user data management system that is external to Adform, you need the ability to map their ID for a given user to the Adform User ID for the same user. 

Audience collection method Description UUID support Taxonomy requirements Available sources
Manual Cookie Import

Manual Cookie import into the selected segment(s).

Adform User ID or Partner UUID. 

If UUID mapping tables are stored on Adform side, you are able to import data using external UUIDS. If they are stored elsewhere, only Adform UUIDs can be used. 

Predefined taxonomy 

  • Ad campaigns (export)
  • Cookie export (Adform DMP)
  • Cookie export from external system (Partner UUIDs)
Direct pixel Profiling pixels are snippets of code that are placed on customer’s website. Only Adform User ID  Predefined taxonomy

  • Websites
  • User engagement
  • Apps
Dynamic Segment Creation

Profiling pixels which dinamically create segments through pixel URL parameters. 

Only Adform User ID  -
  • Websites
  • User engagement
  • Apps
Audience Builder Data collection from Ad campaigns data (impressions, clicks, events) and implemented Site Tracking (TPs, variables). Only Adform User ID  -
  • Ad campaigns 
  • Websites ( requires Site Tracking implementation)
Server to Server File transfer Online and offline data ingestion, no impact on website load latency.

Adform User ID or Partner UUID. 
UUID matching is required 

Predefined taxonomy
  • 3rd party platforms
  • Offline data (CRM, POS, ERP, transactional data etc.)