Troubleshooting for MediaMath

Other Internal Content on MediaMath

Public segment creation is manual for MediaMath. No new destination creation is required. On the segment activation page select "MediaMath Public Destination". Only Price input is required for a public segment. Once segments are created in Unity, the taxonomy needs to be shared with the MediaMath team in the following format:

Note: Add channel segment ID in the code column

full_pathcoderetail_cpmbuyable|zeotap

0|zeotap|France 0|zeotap|France|Demographic

0|zeotap|France|Demographic|Age: 18-24405001.21 https://drive.google.com/file/d/1Q3Kp-1jQ7uYMZ3–epRlCz164HMozQfs/view

IMPORTANT: NEW UPDATES FROM MEDIAMATH -

We need to be whitelisted for each organization for whom we want to create a permission taxonomy/send segments for the first time. A ticket needs to be raised with Mediamath support team for the same. Details below:

https://mediamathsupport.force.com/ Username: [email protected] Password: Zeotap@2019

1 segment can only be attached to 1 destination.

PLEASE DO NOT USE SPACES IN THE AGENCY/ADVERTISER NAME WHILE CREATING DESTINATIONS. Use 'underscore' or

'camelspacing' as separators. This is causing issues with data file parsing at Mediamath's end which was not informed to us earlier. I will update till this is handled as part of the code.

NOTES

The zeotap ID that you see in the segment listing is the internal ID associated with the 1st channel which was added for that segment. Every time a new channel is added, a different ID is associated with it but is currently not reflected in the UI. This information has been added as a new column to the excel report which can be exported from Unity. Adding this to the channel card may be confusing to users who do not have context about the internal ID concept.

Mediamath wants us to send a Taxonomy name for every new destination for which we start sending segments. They return

a taxonomy ID for this taxonomy name which is used for subsequent updates to the taxonomy when we add new segments. The caveat is each unique (org id + agency id + advertiser id) combination which comprises a destination can only have 1 taxonomy name and therefore 1 taxonomy ID. Unity considers each destination as a unique reference point. Since taxonomy name is compulsory and has to be unique, we use either the AdvertiserName or AgencyName provided in the destination as the taxonomy name. For the same client if there are two destinations under two orgs, the advertisername/agencyname has to be the same, since once taxonomy name is added it cannot be changed and Mediamath API will throw an error if we send a different name the next time we send a request.

How private segment creation works for Mediamath:

1. Mediamath requires us to send the following information while sending taxonomy requests along with segment information: Org/Agency/Advertiser IDs (known as permission) unique taxonomy name corresponding to the permission.
2. The first time we send segment creation request for a particular Org/Agency/Advertiser ID combination Destination, we send the above information. Mediamath in return sends us a Taxonomy ID. Going forward, for any new segment creation for the same Org/Agency

/Advertiser ID combination, we need to use the same Taxonomy name and Taxonomy ID. These two fields once generated cannot be edited by zeotap.

1. The Org/Agency/Advertiser IDs are picked from the destination details itself. For taxonomy name we cannot randomly generate a name, since we will not be able to track them for later use. Hence Agency/Advertiser Name provided in the Destination details is used in the taxonomy name sent in the request.
2. If a Destination A was created with Org ID 1, Agency ID 2, Advertiser ID 3, Advertiser Name : Advertiser1 and a Segment X was created for the combination, Mediamath returns a Taxonomy ID 123. This taxonomy ID is stored against Org ID 1, Agency ID 2, Advertiser ID 3 combination. Then a new Destination B is created with Org ID 1, Agency ID 2, Advertiser ID 3, Advertiser Name : Advertiser2. Now if we send Taxonomy ID 123 with taxonomy name Agency2, Mediamath API will detect conflict and the request will fail.

HMMIL_OFF_ITALY destination:

For the above destination we need to send a taxonomy file to MM support, as pushing segments through Unity/Converged will fail. The process is as follows:

• 1. Push segments through Unity UI and theu will fail.
  2. Update the taxonomy file with pushed segments: https://docs.google.com/spreadsheets/d

/1_Rl_e8ynrZOtZF3342FwcXkfi4xRZLGwRUbLIfS84xQ/edit?usp=sharing

• 1. Send a taxonomy file to MM support (https://mediamathsupport.force.com/s/submit-a-case)
  2. Inform Sumi after MM confirms they've updated the taxonomy, as she needs to change segments on our end. You have to raise a task with segment details in Jira under Targeting project and assign it to Sumi. Subject: update mediamath segment details.

Data Upload

Data upload for new segments would be the same as other channels which is within 24 hours. For data refresh, the frequency is once in 30 days as per our contract.

Mediamath also has a 5 GB daily upload limit currently which might get increased later. So ensure that we do not create a more than 20 segments on the same day.

The daily upload limit has been increased to 15 GB now. Please restrict the daily segment creation to 75 segments for now.

Reporting

Reporting is offline and is received by the 7th of the next month. Shared with [email protected].