Data Onboarding

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

Use cases for data onboarding include:

  • 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

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

  • An SFTP account, including username and password
  • A MediaMath namespace, represented by two characters
  • A MediaMath user account, associated with an email address
  • A MediaMath API client ID and secret
  • A MediaMath vendor ID
  • A MediaMath partner organization ID

All data providers distributing data to MediaMath need a MediaMath vendor account and a partner organization account. The vendor account organizes your data for use in our systems and, for 3rd party data providers, will be referenced for revenue share purposes. The partner organization account provides control and access to you and your teams working with MediaMath.

There are several steps to prior to onboarding data with MediaMath:

  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). Prior to reaching out to the partnerships team, familiarize yourself with the MediaMath Audience Data Policy and server-to-server data delivery requirements.
  2. Deploy MediaMath provided sync tag. 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 so that the data provider can refer to a user by their MediaMath Unique User ID (MM UUID). NOTE: For mobile advertising IDs (MAIDs), there is no syncing process required and the MAIDs can be provided directly to MediaMath, provided the correct declaration within the file header.
  3. Deliver a sample file. Upload a sample file via SFTP for approval. Once vetted, the partnerships team will whitelist your account for data delivery to MediaMath.
  4. Access the MediaMath API. Reach out to developers@mediamath.com to gain API access for your organization. Using the data account credentials provided by the partnerships team & API client ID and secret, begin your integration development and testing.

Upon confirmation of successful test file delivery and API requests, by the partnerships team, access to deliver data on behalf of MediaMath customer accounts will be granted.

Required Information

  • Describe your data:
    • is it first-party, meaning it is proprietary to a single entity and will only be made available to that entity;
    • is it third-party, intended for activation by any number of brands &/or agencies; is it both?
  • If first-party, which mutual customers will be onboarding data to MediaMath from you?
  • If third-party, what categories (i.e. Interest, Intent, etc.) or industries (F&I B2B) do you represent?
  • Do you plan to permission data across many advertisers, or specifically for each client to use their own data?
  • Do you plan on billing for data usage?
  • What region(s) are represented in your data set (i.e. NA, LATAM, MENA, etc.)
  • What is the estimated volume of segment data, in GB?
  • How will segment updates (e.g. existing users added to new segments, new users added to existing segments, etc.) be delivered?
    • Incrementally or segment refresh?
    • At what frequency will data be sent?
  • How many segments will you be sending?