OpenAdLibraryOpenAdLibrary
Definition

SupplyChain Object (schain)

The SupplyChain Object (schain) is an OpenRTB field that lists, in order, the sellers and resellers a bid request declares in the direct flow of payment for the inventory, so buyers can check the supply path.

SupplyChain Object (schain) — ad-tech glossary illustration

The SupplyChain Object (schain) is a structured field within an OpenRTB bid request that lists, in order, the sellers and resellers involved in the direct flow of payment for the inventory. In a complete chain, the first node is the owner of the site or app (the publisher) and the last node is the entity sending the bid request. Specified by the IAB Tech Lab, it makes that declared selling path machine-readable. It is not a log of every system an impression touched, and the companies that build the chain supply its contents.

How it works#

The object contains a complete flag, a version string and an array of nodes. Each node represents one seller or reseller in the payment flow and carries the advertising system's canonical domain (asi), the seller's account ID in that system (sid), a payment-flow flag (hp, which should always be 1 in version 1.0) and optional fields such as the request ID and business name. The nodes are listed in the order of the selling chain, so a buyer can read the declared route from the first known seller to the entity sending the request. The complete flag is set when the chain is created and carried forward by resellers: 1 means the originating seller declares that the chain holds every node back to the owner of the site or app, and 0 means it does not. A reseller that receives a request with no SupplyChain object starts one with complete set to 0. The flag is a declaration, not proof that no seller is missing.

Why it matters#

ads.txt lets a publisher list who is authorized to sell its inventory, but the schain specification notes that it does not reveal or authorize all the parties that transact an impression. sellers.json lets an advertising system identify the sellers behind its seller IDs. Schain adds the declared path for one bid request. Buyers can compare each node's domain and seller ID with the exchange's sellers.json and the publisher's ads.txt, and can count how many sellers and resellers sit between the publisher and the request. The specification defines no field for fees, so the object does not show what each party takes. The IAB Tech Lab describes the aim as letting buyers check that intermediaries are entities they want to transact with and that inventory is bought as directly as possible, which feeds supply path optimization across the ad supply chain. Because the participants declare the chain, it is one input to checks on undeclared reselling and fraud, not a guarantee against them, and it only helps where sellers and exchanges implement it.

Related terms: ads.txt, sellers.json, OpenRTB, and Ad Supply Chain.

The OpenAdLibrary Team
Written byThe OpenAdLibrary Team
Ad intelligence & native advertising research

We build OpenAdLibrary, the open ad-transparency platform. Every day our systems capture live native ads across Taboola, Outbrain, MGID, Revcontent, Teads, Yahoo and MSN, identify the real advertiser behind each one, and follow the click to its landing page. These guides distill what we see in that data so you can research the market faster.