Segment Creation

Creation is an automated process through Unity. In Unity, to create a public simply select Oath as a Channel and distribute the . No additional details are required.

For private s, the Client Seat ID field needs to be filled. In Oath's taxonomy Client Seat ID refers to MDM ID of the advertiser.

MDM ID: 22304 is the public seat for Oath. For private s, please ask the client to provide their MDM ID and create the corresponding destination in .

NOTE: PLEASE ASK THE CLIENT TO SEND A SCREENSHOT WITH A MDM ID TO AVOID FAILURES. HERE ARE THE 2 TYPES OF MDM IDS SUPPORTED BY OATH:

1. Advertiser MDM ID's

#1 - This is used either within the global managed seat, where the activity spans across many agencies and/or advertisers or within a client (self serve) seat where the client would like the data shared to specific advertisers and not the whole seat.

1. Seat MDM ID's

#2 - Self-explanatory. When data is shared to this seat, it will be made available to all advertisers.

IMPORTANT:

1. Oath has a restriction at their end where if a is created with incorrect MDM ID apart from that not being visible on their UI, all subsequent s which were created are also impacted and not visible at their end. This is because we are required to send the full taxonomy to Oath everytime a new is created and Oath cannot process any new entries after the incorrect entry. Please always ensure that the client shares the MDM ID with us and not the Advertiser ID. In case you realise that a was created with an incorrect MDM ID, please archive that and create a new one with the correct ID as adding a new destination with the incorrect ID to the same will still result in the incorrect ID being present in the taxonomy. (as long as the s still have the destination with the incorrect ID attached to them in Unity, they will be a part of the taxonomy and hence any subsequent updates with correct IDs will fail. Hence it is important that the existing s with the incorrect destination are first archived and then the new s are created)
2. Oath wants us to follow a structure to our taxonomy which would make it easier for users to navigate through our s and also enable better discovery. The structure proposed is as follows:

Targeting Standard s: The current structure we follow is completely fine for them and we can continue using it : zeotap > Country > Cat > Sub-Cat > Value

Targeting Custom s: They want us to add a "Custom" node to the name so that all custom s are placed under their Custom folder: zeotap > Country > Custom > ....

Connect s: They want us to follow the zeotap > Country > structure for all s we create. Please follow the zeotap >

Country > Custom structure for connect s wherever possible as long as the clients do not specify otherwise.

Pricing of s and Reporting

Pricing of s has to be shared with Oath over email. For a new batch of s, we need to send over a taxonomy file with the following details: ID, Name, (USD only). Send the email to [email protected]

Oath does not have a reporting . Monthly revenue report would be shared with zeotap's reporting alias.