IAB Tech Lab on November 18, 2026 published OpenRTB v2.6-202611, a dated release of the real-time bidding protocol that changes what the SupplyChain object is for. Version 1.1 of the object, which travels inside programmatic ad requests, now covers companies that hold or route a request without handling payment for the inventory, and a new value of the "complete" flag tells buyers whether those companies are all accounted for.
In Short
IAB Tech Lab updated the rulebook that ad auctions use so the record of who handled an ad request can include companies that never pay or get paid for the ad space. That matters to anyone who buys ads by looking at how many companies sit between them and the website, because the record will get longer once companies start using the new rule. The rules for checking those extra companies against the industry's lists of authorised sellers have not been written yet and are due early in 2027.
The record changes its purpose
The SupplyChain object has existed for seven years as a list of companies that touch the money. Each entry, or node, names an advertising system and the seller account it pays. A buyer reading the list could check each node against the publisher's ads.txt file and each exchange's sellers.json file, and so confirm that the inventory was being sold by companies the publisher had authorised.
Version 1.1 widens that list. "Supply Chain 1.1 is now live and discloses any entity that has custody of the bid request," Hillary Slattery, Sr. Director, Programmatic, Product Management at IAB Tech Lab, wrote in a post titled "Updating the Supply Chain Object. Finally." The post carries no publication date on the page; it links to the November 18 release. "Specifically entities that have the ability to initiate or route bid requests to another entity," she added.
The post states the test plainly. "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." Capacity, not behaviour, is what counts. A company that could alter a bid request but leaves it untouched still qualifies.
The previous rule was narrower. "Until today, only companies that either received or cut a check were required to list themselves. That changes with this update," according to the post. The specification text tells the same story. In the June 2026 release, the object list described SupplyChain as a "Chain of nodes from beginning to end representing the entities involved in the direct flow of payment for inventory." In the November release, the same line reads: "Chain of nodes from beginning to end representing the entities that took custody of a bid request."
What changed in the specification
The release notes summarise the change in two lines: "Updated Object: SupplyChain and Object: SupplyChainNode to schain v1.1" and "New complete values: 1 = payment complete, 2 = payment and non-payment complete". The full definitions sit in sections 3.2.25 and 3.2.26 of the OpenRTB 2.6 specification on GitHub. The table compares the wording in release 2.6-202606, the previous tagged version, with release 2.6-202611.
| Element | OpenRTB 2.6-202606 (SupplyChain 1.0) | OpenRTB 2.6-202611 (SupplyChain 1.1) |
|---|---|---|
| Object summary | "Chain of nodes from beginning to end representing the entities involved in the direct flow of payment for inventory." | "Chain of nodes from beginning to end representing the entities that took custody of a bid request." |
| Scope of the chain | "represents all entities who are involved in the direct flow of payment for inventory" | "represents all entities who take custody of a given bid request" |
ver (string, required) |
Example value for version 1.0: "1.0" | Example value for version 1.1: "1.1" |
complete (integer, required) |
"0 = no, 1 = yes" | "0 = not complete"; "1 = payment complete; the SupplyChain object was created by the initial advertising system and includes all hp=1 nodes; some or all hp=0 nodes may be missing"; "2 = payment and non-payment complete; the SupplyChain object includes all hp=1 nodes and all hp=0 nodes" |
nodes (object array, required) |
"Array of SupplyChainNode objects in the order of the chain. In a complete supply chain, the first node represents the initial advertising system and seller ID involved in the transaction, i.e. the owner of the site, app, or other medium. In an incomplete supply chain, it represents the first known node. The last node represents the entity sending this bid request." | "Array of SupplyChainNode objects appended in supply-chain order from seller to buyer." |
hp (integer) |
Defines 1 and 0, then: "For version 1.0 of SupplyChain, this property should always be 1. Implementers should ensure that they propagate this field onwards when constructing SupplyChain objects in bid requests sent to a downstream advertising system." | Keeps the definitions of 1 and 0; the "always be 1" sentence and the propagation sentence are removed |
| Link to implementation examples | Points to supplychainobject.md in the OpenRTB repository | Removed from both object descriptions |
| JSONPath location | None | $.source.schain and $.source.schain.nodes[*] |
asi, sid, rid, name, domain, ext |
Defined | Wording unchanged |
Source: OpenRTB 2.6 specification text at tags 2.6-202606 and 2.6-202611 on GitHub. Comparison by PPC Land.
Two details in that table deserve attention. The first is the value 1. Under version 1.0, "complete": 1 simply meant the chain was complete, because only payment nodes existed. Under 1.1, the same value means something narrower: every payment node is present, but "some or all hp=0 nodes may be missing." A chain marked 1 is therefore no promise that every company with custody of the request has been listed. Only a 2 makes that claim.
The second is the hp flag. In version 1.0 it was a field with only one legal value. The specification said it "should always be 1", and the separate implementation document for the object, still published in the OpenRTB repository, explains that the field was required anyway because future versions were expected to introduce non-payment handling nodes. Version 1.1 is that future version. A node with hp set to 0, in the specification's words, "is not involved in the flow of payment for the inventory."
The node fields themselves did not move. The asi field still holds "The canonical domain name of the SSP, Exchange, Header Wrapper, etc system that bidders connect to," and sid still holds the seller or reseller account identifier, which "Should be limited to 64 characters in length." The name field is still defined as "The name of the company (the legal entity) that is paid for inventory transacted under the given seller_ID", payment language that sits unchanged next to the new non-payment nodes.
How the object is built under version 1.1
According to the specification, a SupplyChain object in an OpenRTB 2.6-202611 bid request is assembled as follows.
- The object sits at
source.schainin the bid request, recorded in JSONPath as$.source.schain. Each node sits at$.source.schain.nodes[*]. - The
verfield carries the string "1.1". - Nodes are "appended in supply-chain order from seller to buyer." Each node identifies the advertising system (
asi) and the seller account within it (sid), and may carry the request ID issued by that seller (rid), plusnameanddomainwhere these are not already in the system's sellers.json file. - Each node sets
hp. A value of 1 means "the advertising system in the asi field pays the seller in the sid field, who is responsible for paying the previous node in the chain." A value of 0 means the node is not in the payment flow. - The
completeflag records how much of the chain is present: 0 when the chain is not complete, 1 when it was created by the initial advertising system and holds all hp=1 nodes, and 2 when it holds all hp=1 and all hp=0 nodes.
The post adds the qualifying rule for step 3: an entity that can initiate or route a request, or that can overwrite something already in it, becomes a node. The specification text does not list which kinds of company that covers. Its asi definition mentions header wrappers alongside SSPs and exchanges, which hints at the range of systems involved.
Seven years in the making
None of this arrived suddenly. The object "was added to OpenRTB 2.5 in 2019 as an extension and codified official support in the full OpenRTB 2.6 specification in 2022," according to the post. Adoption among sellers followed quickly. Index Exchange adopted sellers.json and the SupplyChain object in August 2019, passing a schain object to DSPs in every bid request, and Centro said in August 2020 that it would require both standards from exchanges and ad networks, blocking intermediaries that did not comply. Anyone still using the old extension field gets a pointed note in the post: "if you're still sending the ext...it's time to upgrade my friend."
The idea of non-payment nodes was in the original design. "It was even called out when the spec was originally published that at some point non-payment handling entities would also be listed," the post says. "It took 7 years to come to pass, but today is the day."
The current effort began, by the post's count, "9 months and roughly eleventy billion meetings ago" and drew "about 50 participants from across the Programmatic Supply Chain community". The post names publishers, DSPs and verification vendors among them. IAB Tech Lab put SupplyChain v1.1 forward as a proposal on June 23, 2026, with public comment open until August 21, 2026, according to its announcement at the time. The response was heavy. "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," Slattery wrote.
Version 1.1 shipped as part of a dated 2.6 release rather than as OpenRTB 2.7. Under the versioning policy in the repository's README, "As of OpenRTB 2.6-202211, OpenRTB's version number is only incremented on breaking changes," and the specification "is updated approximately once a month if there are non-breaking improvements". The previous tagged release was 2.6-202606.
Hop counting meets a longer chain
Why should a buyer care about entries that move no money? Because the object is used for more than fraud checks. The post is explicit about the gap between the intended use and the actual one. The purpose of ads.txt and sellers.json, it says, "is to fight misrepresentation of inventory in the bidstream." Then: "We acknowledge that in practice the Supply Chain Object is also used for Supply Path Optimization."
Supply path optimization is, in simple terms, the practice of choosing the cheapest or most direct supply path to the same impression. A common shortcut is to count the nodes. The post is sceptical of that shortcut. "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." And it spells out the consequence: "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."
Hop counts already shape guidance and trading rules. IAB Tech Lab's own Programmatic Auction Definitions, finalised in June, describe paths with more than two or three hops as rare and generally suboptimal. PubMatic's supply policy effective October 7, 2026 allows two inbound schain hops for web and app and one for CTV, excluding the Google Open Bidding node from the count, and blocks resellers that send no schain at all. When The Trade Desk launched OpenAds in October 2025, it listed secret hops and multiple hops among the practices it was targeting. All of these rules were drafted when every node in a valid chain marked a payment step.
For a demand-side platform, the post anticipates a code change rather than a policy debate. "DSPs especially, may need to think in terms of IF statements if they're trying to preserve existing payment entity validation logic." Read against the specification, that means separating hp=1 nodes, which can be checked against sellers.json entries for paid sellers, from hp=0 nodes, for which no equivalent check yet exists.
The money involved is not trivial. IAB Spain's first SSP guide, published in April, put advertiser delivery at 70% to 80% through a direct SSP connection, against 40% to 50% for indirect multi-reseller paths. DataBeat found in September that resellers added 44,608 ads.txt lines across the top 50,000 US publishers, against 10,334 direct lines. Buyers have been acting on what the bidstream tells them: the Coalition for Innovative Media Measurement reported on November 12 that 62% of programmatic CTV buyers move spend to another path when the signals they need are missing.
Validation is the unfinished half
The OpenRTB change is only one of two parts. "This is just the first of at least two planned releases relating to the inclusion of non-payment handling entities in the supply chain," the post says. "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 order was deliberate. "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," according to the post.
Validation is where the hard questions sit. "A core piece of feedback from Public Comment was that the specification really needs to nail how to validate these new nodes," Slattery wrote. "There are multiple ways to go about said validation, and the group is working through the available options." The post says a Public Comment period on the sellers.json and ads.txt changes should be expected early next year, and points readers to IAB Tech Lab's GitHub, where "(app)/ads.txt and sellers.json now live."
The existing checks already struggle. IAB Tech Lab's Programmatic Best Practices v1.0, released in September, ask sellers to include an schain object in each bid request and cite a HUMAN Security diagnostic in which 79% of requests carried a SupplyChain object, but only 42% of those passed full validation. Across 2,054 European news publishers, IAB Europe found ads.txt files on 72.64% in August 2025, with about 79% of valid lines matching a sellers.json entry. The new hp=0 nodes arrive before sellers.json has any rules for describing them.
The rest of the release
The schain change headlines a release that carries four other groups of changes.
| Area | Change in 2.6-202611 | Detail |
|---|---|---|
| JSONPath | "Added JSONPath (RFC 9535) locations to all Bid Request and Bid Response objects" | 38 object definitions now open with JSONPath expressions: 35 bid request objects (sections 3.2.1 to 3.2.35) and 3 bid response objects (4.2.1 to 4.2.3). Objects carried inside ext are not listed. |
| CTV Ad Portfolio Signaling | "New Implementation Guidance pointer for pause, menu, overlay, squeezeback, in-scene and screensaver formats" | New section 7.17 in the implementation guide links to the signaling guidelines in IAB Tech Lab's ad format repository |
| Protobuf | "Added content.realtime and content.firstbroadcast"; "Added Agentic Audiences extension (segment.ext.aa)"; "Matched OpenRTB 2.x.md updates" | Both content fields were already defined in the June JSON specification as 0/1 values; the Protobuf schema now carries them |
| Example fixes | "Corrected bid request and bid response examples (banner, DOOH video, expandable creative, video)" | The expandable creative example now nests a data value inside a segment array; the video example uses the api field the Video object defines; the banner and DOOH video response examples now carry valid markup in adm |
| Appendix A | "Fixed Google Metro Codes link" | The reference moves from a Google Ads API geotargets page to the geo table referenced in Google's Authorized Buyers OpenRTB guide |
Source: GitHub release notes for OpenRTB v2.6-202611 (quoted) and the specification and implementation files at the 2.6-202611 tag. Detail column by PPC Land.
JSONPath gives every field a fixed address. According to the specification, $ is the top-level BidRequest object and [*] selects every element of an array, so $.imp[*].banner.format[*].w is "the width of each allowed banner size." The change follows IAB Tech Lab's decision in September to move its specifications from PDF to Markdown on GitHub.
The CTV pointer refers to work finalised earlier in the year. IAB Tech Lab finalised signaling for six CTV formats on July 22: pause, menu and home screen, overlay, screensaver, in scene and squeezeback. The OpenRTB release adds only a pointer to those guidelines, not new fields.
The Protobuf addition of Agentic Audiences is the newest element. The extension document in the OpenRTB repository lists LiveRamp and Raptive as sponsors and describes Agentic Audiences as the standard formerly called the User Context Protocol, which LiveRamp donated to IAB Tech Lab in November 2025. It carries embeddings, compact numeric representations of a consumer's signals, inside the existing user data segments of a bid request.
| Field in segment.ext.aa | Type | Content, according to the extension document |
|---|---|---|
ver |
string | Specification version for embedding schema compatibility, for example "1.0.0" |
vector |
string | Base64-encoded embedding of little-endian Float32 values |
dimension |
integer | Number of Float32 values; must equal the decoded byte length divided by 4 |
model |
string | Identifier of the model that produced the embedding |
type |
integer array | 1 = identity, 2 = contextual, 3 = reinforcement |
What the documents leave open
The release and the post do not say how a downstream system can confirm that every hp=0 node is present before a chain is marked 2, which sellers.json fields will describe non-payment entities, or when SSPs and DSPs are expected to support version 1.1. The companion implementation document for the object, still in the OpenRTB repository, describes version 1.0 and has not been updated, and the specification no longer links to it. No adoption figures or timetable beyond "early next year" were given.
Key facts
- Release: OpenRTB v2.6-202611 (tag 2.6-202611, commit dbfe66c), published on GitHub on November 18, 2026: https://github.com/InteractiveAdvertisingBureau/openrtb2.x/releases/tag/2.6-202611
- Previous tagged release: OpenRTB 2.6-202606
- Object version: SupplyChain (schain) 1.0 to 1.1;
vervalue "1.1" - Specification sections: 3.2.25 (Object: SupplyChain) and 3.2.26 (Object: SupplyChainNode)
- JSONPath:
$.source.schainand$.source.schain.nodes[*] completevalues: 0 = not complete, 1 = payment complete, 2 = payment and non-payment completehpvalues: 1 = node in the payment flow, 0 = node not involved in the flow of payment- Inclusion test, per IAB Tech Lab: any entity able to initiate or route a bid request, or to overwrite something already in it
- Accompanying post: "Updating the Supply Chain Object. Finally." by Hillary Slattery, Sr. Director, Programmatic, Product Management, IAB Tech Lab; no date shown on the page: https://iabtechlab.com/updating-the-supply-chain-object-finally/
- Working group size: about 50 participants, effort begun about nine months before the release, per the post
- Proposal: SupplyChain v1.1 proposed June 23, 2026; public comment closed August 21, 2026
- Next step: sellers.json and (app)/ads.txt updates and a Public Comment period planned for early 2027
- Other release items: JSONPath (RFC 9535) on 38 objects; CTV Ad Portfolio Signaling pointer (section 7.17 of the implementation guide); Protobuf content.realtime, content.firstbroadcast and Agentic Audiences extension (segment.ext.aa); example and link fixes
Timeline
- 2019: SupplyChain object added to OpenRTB 2.5 as an extension
- August 2019: Index Exchange adopts sellers.json and the SupplyChain object
- August 2020: Centro says it will require sellers.json and the SupplyChain object
- 2022: SupplyChain object codified in the full OpenRTB 2.6 specification, with hp expected always to be 1
- August 7, 2025: IAB Europe finds ads.txt on 72.64% of 2,054 European news publishers
- October 2, 2025: The Trade Desk announces OpenAds, naming secret hops among targeted practices
- November 3, 2025: LiveRamp donates the User Context Protocol to IAB Tech Lab
- About February 2026: IAB Tech Lab effort on non-payment nodes begins, by the post's count
- April 15, 2026: IAB Spain publishes its first SSP guide
- June 2026: OpenRTB 2.6-202606 released, the last version with SupplyChain 1.0
- June 2026: IAB Tech Lab finalises its Programmatic Auction Definitions
- June 23, 2026: IAB Tech Lab proposes SupplyChain v1.1 and opens public comment
- July 22, 2026: IAB Tech Lab finalises signaling for six CTV ad formats
- August 21, 2026: Public comment on SupplyChain v1.1 closes
- September 2026: IAB Tech Lab moves its specifications from PDF to Markdown on GitHub
- September 16, 2026: Programmatic Best Practices v1.0 ask for an schain object in each bid request
- September 18, 2026: DataBeat counts 44,608 new reseller ads.txt lines against 10,334 direct
- October 7, 2026: PubMatic supply policy caps inbound schain hops at two for web and app, one for CTV
- November 12, 2026: CIMM reports 62% of CTV buyers move spend when signals are missing
- November 18, 2026: OpenRTB v2.6-202611 published with SupplyChain 1.1
- Early 2027: sellers.json and (app)/ads.txt updates and a Public Comment period planned
Related PPC Land coverage
- IAB Tech Lab finally defines what a programmatic auction actually is - The final definitions set a 12-step workflow in which ads.txt, sellers.json and the supply chain object are validated at the request stage.
- IAB Tech Lab sets rules to curb duplicate ad bid requests industry-wide - Programmatic Best Practices v1.0 ask for an schain object in every bid request and cite a diagnostic where 42% of chains passed full validation.
- PubMatic cut its excess inventory fee 80% in April, page history shows - PubMatic's October 7 policy limits inbound schain hops and blocks resellers that send no schain.
- Trade Desk launches OpenAds to counter supply chain manipulation - The Trade Desk framed its Prebid fork as a response to secret hops, multiple hops and request duplication.
- Resellers gain 44,600 ads.txt lines to direct's 10,300, DataBeat finds - Reseller entries made up about 81% of net ads.txt growth among the top 50,000 US publishers.
- IAB Spain's first SSP guide exposes the 41% working media problem - The guide compares delivery through direct and multi-reseller paths and frames SPO around schain checks.
- Silence in the bidstream sends 62% of CTV buyers elsewhere, CIMM finds - CIMM found most CTV buyers shift spend to other supply paths when bidstream signals fall short.
- European publishers show 73% adoption of supply chain transparency standards - IAB Europe measured ads.txt and sellers.json coverage across 2,054 news publishers.
- Trade Desk gains direct CTV pause ad supply as IAB finalizes 6 format signals - The six CTV format signals that the new implementation pointer refers to.
- IAB Tech Lab drops PDF as the source of truth for its ad standards - IAB Tech Lab moved its specifications to Markdown across public GitHub repositories.
- LiveRamp donates User Context Protocol to IAB Tech Lab for agentic advertising - The embedding protocol now carried in OpenRTB as the Agentic Audiences extension.
- Index Exchange adopts sellers.json & SupplyChain - An early adopter of the two transparency standards in 2019.
- Centro to require sellers.json and SupplyChain Object - A buyer's 2020 move to make both standards a condition of trading.
Summary
Who: IAB Tech Lab and its Programmatic Supply Chain Commit Group, with about 50 participants from publishers, DSPs and verification vendors. The change affects systems that initiate or route bid requests, and the buyers and DSPs that read the SupplyChain object.
What: OpenRTB v2.6-202611 updates the SupplyChain object to version 1.1. The chain now covers every entity with custody of a bid request, adds hp=0 nodes for entities outside the payment flow, and redefines the complete flag as 0, 1 (payment complete) or 2 (payment and non-payment complete). The release also adds JSONPath locations to 38 objects, a CTV Ad Portfolio Signaling pointer, Protobuf fields including the Agentic Audiences extension, and example fixes.
When: The release was published on GitHub on November 18, 2026. The proposal was opened for public comment on June 23, 2026 and closed on August 21, 2026. Updates to sellers.json and (app)/ads.txt are planned for early 2027.
Where: In the OpenRTB 2.x specification repository on GitHub, at $.source.schain in every OpenRTB 2.6 bid request that carries the object.
Why: The original specification anticipated non-payment nodes, and IAB Tech Lab says the object should disclose every entity able to route or alter a request. Because buyers also use the object for supply path optimization, the longer chains will affect hop-count rules and DSP validation logic, while the rules for validating the new nodes are still being written.
Discussion