Seller json Supply Chain Object Office Hours CONFIDENTIAL

Seller. json & Supply Chain Object Office Hours CONFIDENTIAL & PROPRIETARY

SELLERS. JSON CONFIDENTIAL & PROPRIETARY 1

SELLERS. JSON PROBLEM SOLUTION RESULT Buyers and intermediaries have no visibility into chain of inventory § Ad systems post the seller info on their root domain Buyers and intermediaries can cross check sellers information § Sellers. JSON will list all the valid seller information CONFIDENTIAL & PROPRIETARY Suspicious vendors in supply chain will become apparent 2

SELLERS. JSON IN PUBLIC COMMENT seller_id Sellers Identifiers contact_email contact_address version ext Directness Required Attribute Optional Attribute is_confidential name domain comment ext CONFIDENTIAL & PROPRIETARY Required for non confidential sellers

SELLERS. JSON IN PUBLIC COMMENT seller_id Sellers Directness -> seller_type Required Attribute Identifiers is_confidential Optional Attribute contact_email name Required for non confidential sellers contact_address domain version ext comment ext is_passthrough* CONFIDENTIAL & PROPRIETARY * = New Addition

What should be the seller_type? CONFIDENTIAL & PROPRIETARY

Who should use is_passthrough? CONFIDENTIAL & PROPRIETARY

SELLER. JSON EXAMPLE CONFIDENTIAL & PROPRIETARY

SELLER. JSON EXAMPLE Continued CONFIDENTIAL & PROPRIETARY

SELLER. JSON EXAMPLE Continued CONFIDENTIAL & PROPRIETARY

o. RTB SUPPLY CHAIN OBJECT CONFIDENTIAL & PROPRIETARY 10

ORTB SUPPLY CHAIN OBJECT PROBLEM Buyers and intermediary systems have no visibility into the supply chain SOLUTION RESULT Every entity that splits ad dollar will be added as node in schain Buyers and intermediary tech systems can parse the information to gain transparency into money trail CONFIDENTIAL & PROPRIETARY 11

ORTB SCO IN PUBLIC COMMENT PERIOD asi complete pid Required Attribute nodes rid Optional Attribute name domain ext CONFIDENTIAL & PROPRIETARY

o. RTB SCO v 1 asi complete pid -> sid nodes rid version* ext* name domain hp* ext CONFIDENTIAL & PROPRIETARY Required Attribute Optional Attribute * = New Addition

o. RTB EXAMPLE 1: . Originating bid request CONFIDENTIAL & PROPRIETARY

o. RTB EXAMPLE 2: . Bid. Request 1 resold by Pub. Matic CONFIDENTIAL & PROPRIETARY

o. RTB EXAMPLE 3: . Request with out SCO CONFIDENTIAL & PROPRIETARY

o. RTB EXAMPLE 3: . Non SCO compliant Bid. Request 4 resold by Pub. Matic CONFIDENTIAL & PROPRIETARY

IMPLEMENTATION SUMMARY § It is invalid for a reseller to copy the Supply. Chain object from the previous seller to their request for that inventory - without also inserting their information into the chain. § If a reseller doesn't insert themselves in the chain, their bid request should not include the Supply. Chain object. § If a seller is reselling inventory that didn't previously contain a Supply. Chain object, they should create the Supply. Chain object themselves, mark the "complete" attribute with a value of "0" and insert their node into the "nodes" array. § If a seller is reselling inventory that has a Supply. Chain object, the reseller should copy the existing object - keeping the original value of the "complete" and append their node to the end of the "nodes" array. § If this is the originating bid request for this inventory, the Supply. Chain object should be created with the "complete" attribute set to "1" and their information being the only node in the "nodes" array. CONFIDENTIAL & PROPRIETARY

Non - o. RTB SUPPLY CHAIN OBJECT CONFIDENTIAL & PROPRIETARY 19

o. RTB FOR TAG BASED INTEGRATIONS <script src="https: //ads. exchange 1. com/srv? pid=194&sz=300 x 250&plid=2842181& s. Chain=[SUPPLYCHAIN GOES HERE]"> </script> CONFIDENTIAL & PROPRIETARY

o. RTB FOR VAST URL https: //ads. exchange 1. com/srv? pid=194&sz=v&plid=2842185& s. Chain=[SCHAIN GOES HERE] CONFIDENTIAL & PROPRIETARY

Serialization of an SChain version , complete ! Node 1 CONFIDENTIAL & PROPRIETARY ! Node 1

Serialization of an SChain version , complete sid asi , ! Node 1 rid , name , CONFIDENTIAL & PROPRIETARY domain , ! Node 1 hp , ext ,