Data Onboarding

Data onboarding uses a server-to-server process to import data and an API to create and modify the structure of that data and its associated permissions which control access to the data in TerminalOne. Integrate your first- and third-party audience data sets with control and transparency to organize and activate audiences in TerminalOne for increased reach, targeting accuracy, and consistency.

Use cases:

  • Onboard data for targeting - bring your audience segments to TerminalOne for omnichannel media activation. This self-service solution gives you control and is designed to enable easy ingestion, search, and targeting of segments.
  • Onboard data for reporting and analysis - import your first party data for enhanced analytics with Modular Dashboard.
  • Onboard data for measurement, attribution and optimization - bring your first party audience data sets to Data Mining Console to model audiences based on your first party data sets and MediaMath campaign data.

What to Expect During the Setup Process

There are several steps to getting started with data onboarding:

  1. Engage with the partnerships team. They will ask to review the required information below, help you establish data vendor account credentials and, in some cases, determine the structure of a commercial agreement (i.e. for 3rd party data providers).
  2. For cookie-based data onboarding: MediaMath and the data provider must sync identifiers to allow for use of user data keyed to the consumer’s identity. This is an asynchronous process set up by MediaMath support so that the data provider can refer to a user by their MediaMath Unique User ID (MM UUID). NOTE: For mobile advertising ID (MAID) users, there is no syncing process required and the MAIDs can be provided directly to MediaMath provided the correct declaration within the file header.
  3. Reach out to to gain API access for your company.
  4. Using the provided account credentials & API key, begin your development and testing. For some accounts, this may include a whitelisting process that can take 2-5 business days.
  5. Upon successful file delivery and API requests, confirmed by MediaMath support &/or our Partnerships team, access to MediaMath customer accounts is finalized.

Getting Started Checklist

  • Contact the MediaMath partnerships team
  • Deploy MediaMath provided sync tag
  • Store MediaMath cookie IDs against your user IDs
  • Inform MediaMath whether you’ll be providing a Global Taxonomy, Permissioned Taxonomies, and/or External Data Segments (also known as Data Pixels)
  • Upload a sample file to SFTP for approval
  • Deliver files to SFTP on regular basis
  • Gain MediaMath API access
  • If using Global or Permissioned Taxonomy API, submit sample taxonomy for approval
  • Keep MediaMath informed of changes to Global Taxonomy, Permissioned Taxonomy, and/or External Data Segments (also known as Data Pixels).

Data Vendor Account

Data providers distributing 1st or 3rd party data and customers distributing 1st party data to MediaMath require a MediaMath data vendor account. This account provides control & access to you and your teams working with MediaMath. Additionally, for 3rd party data providers, this account will be referenced for revenue share purposes.

As part of the provisioning process you will receive the following from MediaMath partnerships team:

  • An SFTP location, username, and password
  • A MediaMath user account, associated with an email address
  • A MediaMath API key (visit for more details or contact
  • A MediaMath data vendor ID
  • A MediaMath data organization ID