No. Ads.txt lists authorized sellers for a publisher domain. The SupplyChain Object (schain) records each hop an impression took through sell-side systems in a specific bid request. Buyers use ads.txt for policy and schain for the live transaction path. Together they reduce spoofing and opaque resale.
What is the SupplyChain Object?
Abisola | Feb 20, 2026
The SupplyChain Object (schain) is an IAB Tech Lab structure carried inside programmatic bid requests. It lists each hop an impression took through sell-side systems (nodes with seller IDs and ad system domains). Buyers use it to see the actual path for that auction, not only who is allowed to sell in theory.
What gets passed in schain?
Each node usually includes identifiers such as the advertising system domain (asi), seller ID (sid), and whether the party has a direct payment relationship with the publisher (hp). The object also has a complete flag: when it is incomplete, many buyers treat the request as higher risk because part of the chain may be missing.
SSPs and exchanges append nodes as the request moves. The first hop often comes from the publisher’s primary partner; downstream platforms add their own entries. Demand-side platforms parse the full object at bid time.
How buyers use the chain
Common uses include supply-path optimization (preferring shorter, known paths), matching sid values to public seller files, and blocking inconsistent or opaque chains. That complements static files like ads.txt and exchange-published seller lists, which describe policy, not the live transaction.
Why it matters for ad fraud and invalid traffic
Ad fraud thrives when inventory is misrepresented or arbitraged through hidden intermediaries. schain does not prove a human saw an ad, but it exposes long, noisy, or incomplete paths that often overlap with low-quality or spoofed supply.
Invalid clicks and fake engagement still require dedicated signals: suspicious behavior models, bot and datacenter patterns, and rules tuned to your campaigns. Large buyers often combine schain checks with MRC-oriented measurement practices and third-party verification; for search and social, parallel controls remain important because those channels use different mechanics than open RTB.
Where click quality is the issue, also review suspicious clicks and how they show up next to legitimate traffic. Junk leads from questionable inventory can still occur even when seller files look correct.
Understanding schain also helps teams ask better questions of partners and align with initiatives discussed in resources such as ad fraud prevention guides.
Frequently Asked Questions
Is schain the same as ads.txt?
What if the schain complete flag is 0?
A complete value of 0 means the supply chain may be truncated or missing nodes. Many demand-side platforms throttle, discount, or block those requests because hidden intermediaries raise fraud risk. Incomplete chains often overlap with misrepresented inventory even when static seller files look correct.
Does schain replace fraud filters?
No. Schain exposes supply path length and participant IDs but does not prove a human viewed an ad or clicked legitimately. Invalid clicks and bot engagement still need behavioral models, datacenter IP rules, and campaign-level controls. Treat schain as transparency that complements, not replaces, click quality checks.
How do buyers use schain in practice?
Demand-side platforms parse schain nodes at bid time for supply-path optimization, matching seller IDs to public seller files, and blocking inconsistent chains. Shorter, known paths with complete flags are often preferred. That helps buyers avoid arbitraged inventory that drives junk leads despite correct ads.txt entries.