Updating the Supply Chain Object. Finally.

9 months and roughly eleventy billion meetings ago, an effort that would eventually result in support for adding non-payment handling entities to Object: Supply chain kicked off. This effort brought in about 50 participants from across the Programmatic Supply Chain community (publishers, and DSPs, and verification vendors… OH MY!) who all gave their time, thoughts, and expertise to make this update possible. 

Taking a step back for the uninitiated – (this em dash brought to you by an actual human) Object: Supply Chain was added to OpenRTB 2.5 in 2019 as an extension and codified official support in the full OpenRTB 2.6 specification in 2022. (Tangentially related, if you’re still sending the ext…it’s time to upgrade my friend.) The purpose of the Supply Chain Object is to provide an auditable trail of the path a given bid request took. It’s auditable because we can validate the participants are authorized by the publisher using ads.txt and sellers.json. 

Until today, only companies that either received or cut a check were required to list themselves. That changes with this update. Everyone knew this day was coming. It was even called out when the spec was originally published that at some point non-payment handling entities would also be listed. It took 7 years to come to pass, but today is the day. 

Supply Chain 1.1 is now live and discloses any entity that has custody of the bid request. Specifically entities that have the ability to initiate or route bid requests to another entity. The litmus test here is if you have the ability to overwrite something that was already there (whether or not you actually do it), you will become a node.

This is just the first of at least two planned releases relating to the inclusion of non-payment handling entities in the supply chain. We plan to release updates to sellers.json and (app)/ads.txt early next year. That release will include a metric ton of scenarios and additional rules around when and how to list yourself. The Commit Group made the decision to push just the OpenRTB update now so that implementers have plenty of time to talk about how and when to make these changes. 

I will take this opportunity to note that the purpose of ads.txt and sellers.json is to fight misrepresentation of inventory in the bidstream. We acknowledge that in practice the Supply Chain Object is also used for Supply Path Optimization. When done well, SPO is about finding the most efficient path to a given piece of inventory. What clients deem to be ‘the most efficient’ is up to them, but we know it will always be more nuanced than simple hop counting. When fully rolled out, this update will result in more nodes in the supply chain. Buyers that are relying on blunt strategies will need to revisit that way of thinking to incorporate the additional transparency. DSPs especially, may need to think in terms of IF statements if they’re trying to preserve existing payment entity validation logic.  

If the number of responses on the original Public Comment issue doesn’t tell you how much this will impact the ecosystem, I’m not sure what will. A core piece of feedback from Public Comment was that the specification really needs to nail how to validate these new nodes. There are multiple ways to go about said validation, and the group is working through the available options. While the OpenRTB update is codified, expect a Public Comment period early next year to address any updates to sellers.json and ads.txt. Keep an eye on the GitHub repository where (app)/ads.txt and sellers.json now live. 

Hillary Slattery

Hillary Slattery
Sr. Director, Programmatic, Product Management
IAB Tech Lab