Audience Segment Onboarding

Distribute your first- and third-party audience segments with control and transparency to organize and activate audience data in the MediaMath platform for increased reach, targeting accuracy, and consistency. Data onboarding for audience segments includes cloud-file-transfer, server-to-server and an API to create and modify the structure of that data and its associated permissions.

Use cases for audience segment onboarding include:

• Onboard audience data for targeting and optimization - bring your first-party (1P) and third-party (3P) audience segments to MediaMath for omnichannel media activation, including targeting and optimization. This self-service solution gives you control and enables easy search, targeting, and the application of audiences in Brain, our intelligient optimization engine.
• Onboard audience data for reporting and analysis - import your data for enhanced analytics with solutions like Modular Dashboard.
• Onboard audience data for attribution and measurement - bring your 1P audience data sets for campaign attribution and measurement.

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 vendor account and a partner organization account. The vendor account organizes your data for use in our systems and, for 3P data providers, will be referenced for commercial 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 vendor account credentials and, in some cases, determine the structure of a commercial agreement (i.e. for 3P 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 3P 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 1P cookie IDs, mobile advertising IDs (MAIDs) and Connected TV devices, there is no syncing process required and the IDs can be provided directly to MediaMath, provided the correct declaration within the file header.
3. Deliver a sample file. Upload a sample file for approval. Once vetted, the partnerships team will update your account your account for data delivery to MediaMath.
4. Access the MediaMath API. Reach out to MediaMath Support to gain API access for your company. Using the account credentials provided by the partnerships team & API client ID and secret provided by MediaMath Support, begin your integration API 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 client 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 clients 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 share data across many brands, 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 (APAC, EMEA, LATAM, MENA, NAM)
• 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?
• In total, how many segments will you be distributing to MediaMath?