Troubleshooting for MediaMath

{glossary.AM}ath">Other Internal Content on Mediath

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

Note: Add channel 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 MEDIATH -

We need to be whitelisted for each organization for whom we want to create a permission taxonomy/send s for the first time. A ticket needs to be raised with Mediath support te for the se. Details below:

{glossary.AM}athsupport.force.com/">https://mediathsupport.force.com/ Userne: [email protected] Password: Zeotap@2019

1 can only be attached to 1 destination.

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

'celspacing' as separators. This is causing issues with data file parsing at Mediath'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 listing is the internal ID associated with the 1st channel which was added for that . Every time a new channel is added, a different ID is associated with it but is currently not reflected in the . 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.

Mediath wants us to send a Taxonomy ne for every new destination for which we start sending s. They return

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

How private creation works for Mediath:

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

/Advertiser ID combination, we need to use the se Taxonomy ne 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 ne we cannot randomly generate a ne, since we will not be able to track them for later use. Hence Agency/Advertiser Ne provided in the Destination details is used in the taxonomy ne sent in the request.
2. If a Destination A was created with Org ID 1, Agency ID 2, Advertiser ID 3, Advertiser Ne : Advertiser1 and a X was created for the combination, Mediath 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 Ne : Advertiser2. Now if we send Taxonomy ID 123 with taxonomy ne Agency2, Mediath 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 s through Unity/Converged will fail. The process is as follows:

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

/1_Rl_e8ynrZOtZF3342FwcXkfi4xRZLGwRUbLIfS84xQ/edit?usp=sharing

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

Data Upload

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

Mediath 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 s on the se day.

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

Reporting

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