Why SChain Validation Deserves More Attention Than It Gets

The story. SChain — the OpenRTB supply chain object attached to every bid request — records every entity that touched an impression on its way to auction. Ads.txt, introduced in 2017, confirmed who was authorized to sell a publisher’s inventory. It never confirmed which path a given impression actually took to get there. That gap is what SChain closes, and per InMarket engineering manager Piyush Deolikar, most of the industry still isn’t validating it. (IAB Tech Lab, 15 September 2026)

01What happened

• What SChain records. Defined in OpenRTB 2.6 and later, each hop in the chain declares the advertising system that handled it (asi), the seller ID used (sid), and whether that hop was part of the payment flow (hp); a complete flag says whether the chain traces all the way back to the actual site or app owner.
• The gap it closes. Ads.txt authorizes sellers; it doesn’t expose the route an impression traveled through resold and rebrokered inventory. Deolikar argues that gap is exactly where domain spoofing and obfuscated reselling live.
• The fraud patterns it catches. Fabricated hops with asi/sid pairs that don’t exist in any seller’s sellers.json file; payment-handling nodes missing from the publisher’s own ads.txt; spoofed domains carrying bundle IDs that can’t be resolved or validated; duplicate seller IDs and other silent chain-degradation errors that let a fraudulent node ride downstream undetected.
• Who Deolikar says should act, and how. Exchanges should validate SChain before sending outbound bid requests, to keep DSP partnerships in good standing on “clean, validated” data. SSPs should insert their own node on every request, keep sellers.json synchronized, and drop or flag upstream chains that don’t reconcile rather than pass the risk downstream. DSPs should apply bid-time filters that discount incomplete or unauthorized chains and treat unverifiable chains from non-direct partners as a red flag — what Deolikar calls “the cheapest, highest-leverage fraud filter available.”

02What it means inside a GAM network

SChain validation is the sell-side transparency layer publishers already have the tools to enforce and mostly don’t — every unvalidated hop in your resold inventory is an unpriced fraud liability sitting in your own auction.

For a GAM/AdX publisher, this isn’t a buy-side problem to wait out — it’s a sellers.json hygiene problem inside your own stack. Every reseller path you allow through Authorized Buyers or an open-bidding partner carries a chain that either reconciles against your ads.txt and your partners’ sellers.json files, or it doesn’t. An unreconciled chain is inventory a sophisticated DSP will eventually discount or drop at bid time anyway per Deolikar’s own recommended DSP behavior — so the publisher revenue impact of ignoring SChain isn’t hypothetical, it’s a fill-rate and CPM tax that shows up as unexplained softness on resold inventory specifically.

03What publishers should do about it

04The bottom line

Ads.txt solved “who’s allowed to sell this.” SChain, validated, solves “which route did this impression actually take” — and per Deolikar, most of the industry still isn’t checking. For a publisher running resold or open-bidding inventory through GAM, that’s not a compliance gap to fix someday; it’s an unpriced discount already showing up in DSP bid behavior on exactly the inventory nobody’s validating.