Yield & pricing

SupplyChain 1.1 Is Live In OpenRTB. Every Company That Can Rewrite Your Bid Request Now Belongs In The Chain

Buğra Berat Kavuncu ·4 min read·How we report Share Print
In this piece
    The sealed tags are the ones that were paid; the plain ones held it too, and now they are on the chain.
    The sealed tags are the ones that were paid; the plain ones held it too, and now they are on the chain.

    The story. The SupplyChain object, or schain, is the list inside every OpenRTB bid request that names each company the request passed through on its way to the buyer. Until this week it only had to name the companies in the payment chain. IAB Tech Lab has now published version 1.1 in OpenRTB 2.6, and it widens that to any company that takes custody of the bid request, whether or not it is paid. For a publisher, the chain a buyer sees on your inventory is about to get longer, and buyers will start asking why. (IAB Tech Lab, “Updating the Supply Chain Object. Finally.”)

    01What happened

    • The release. Tech Lab tagged OpenRTB 2.6-202611 on GitHub on 18 November. Its release notes list “Supply Chain Object 1.1” as the first item.
    • The new scope. Under 1.0 the chain covered “all entities who are involved in the direct flow of payment.” Under 1.1 it covers “all entities who take custody of a given bid request.”
    • The test for a node. Tech Lab’s rule: if you can overwrite something already in the request, whether or not you do, you become a node.
    • hp=0 now means something. Under 1.0, the hp (handles payment) flag “should always be 1.” In 1.1, hp=0 marks a node that held the request but was not paid.
    • A three-way complete flag. complete was 0 or 1. It is now 0 for not complete, 1 for every paid node present, and 2 for every paid and unpaid node present.
    • The version string. Chains built to the new rules carry "ver": "1.1". The spec’s own example moved from “1.0” to “1.1”.
    • How long it took. Tech Lab says the change took about 9 months and roughly 50 working group members, and 7 years to come about.
    • What is not done yet. This is the first of at least two releases. Tech Lab plans sellers.json and ads.txt updates “early next year,” with another public comment period.
    • Why it waited. Public comment asked for a clear way to validate the new nodes. That work sits in the sellers.json and ads.txt updates still to come.

    We covered the proposal in June, while it was out for public comment. What follows is about the version that shipped.

    02What it means for a publisher’s supply paths

    Under 1.0, a wrapper, a traffic-shaping service or an identity vendor could sit between your ad server and the SSP. It could add or rewrite fields, and never appear in the chain, because it was not cutting the check. Under 1.1, that company should appear as an hp=0 node. The chain buyers see on your inventory gets longer, but none of those companies are new. They were always there.

    That matters because buyers already use the chain to choose paths. Tech Lab says so plainly: the object “is also used for Supply Path Optimization.” Most SPO rules today count hops and prefer the shortest path. If those rules count hp=0 nodes the same as paid resellers, a path that is now being more honest could score worse than one that is not. Expect a period where a clean direct path shows three nodes and buyers’ tools do not yet tell a custody node from a reseller.

    The complete flag is where buyers will look first. A chain marked 2 says every company that held the request is listed. Being able to send 2 with confidence is the publisher’s new advantage. Sending 1 is still valid. But it tells the buyer some custody nodes may be missing, and some will read that as a gap to price in.

    There is one practical limit. Nothing yet lets a buyer check an hp=0 node against a file the way hp=1 nodes are checked against sellers.json. Tech Lab’s own post says validation is the work still to come. Until then, the new nodes are only as reliable as the company that adds them.

    SupplyChain 1.1 moves the chain from "who got paid" to "who held the request.

    03What publishers should do about it

    04The bottom line

    SupplyChain 1.1 moves the chain from “who got paid” to “who held the request.” That is a fairer picture, and it favours publishers who know their own stack. In the short run it will make some honest paths look longer. Map your custody nodes, ask your SSPs what they will send, and explain the extra nodes to buyers before an SPO rule does it for you.

    Related: CTV Buyers Move Spend When Bid Requests Miss Signals. CIMM Wants A Baseline Publishers Can Check

    Sources & caveats

    Sources: IAB Tech Lab, “Updating the Supply Chain Object. Finally.” (Hillary Slattery, November 2026), for the custody test, the working group figures, the release plan and the validation point. IAB Tech Lab, OpenRTB 2.6-202611 release notes (18 November 2026), and OpenRTB 2.6 specification, sections 3.2.25 and 3.2.26, compared with the 2.6-202606 text, for the field changes. The reading for publishers and the recommendations are APH desk analysis.

    The weekly

    One letter a week, from the desk that runs the auctions.

    What actually moved in yield, CTV and curation across our publishers — written by the people who saw it, not a content team. No digests, no roundups, one email.

    One email a week. Unsubscribe in one click. We never share or sell the list.

    More from this issue

    Ran alongside this piece in the Weekly of 20 November 2026.