Volume navigation
Supply Chain · supply chain transparency
ads.txt 1.1 · sellers.json 1.0 · SupplyChain objectOn this page
Why an ad chain needs supply chain transparency standards
A bid request has to answer three questions about supply: whether the seller of this inventory is authorized to sell it, which legal entity stands behind that account, and which parties this transaction actually passed through. The three are carried by different standards and must line up with one another — when they do not, the path cannot be judged trustworthy.
Authorization and identity are two different things. Authorization says an account is allowed to sell a given set of inventory, and is declared by the publisher under a domain it controls; identity says which legal entity that account belongs to and whether it is a direct seller or an intermediary, and is disclosed by the advertising system under its own domain. If either side is missing the other cannot be checked: authorization without identity leaves the buyer not knowing whom it is transacting with, and identity without authorization cannot confirm that the entity has any right to sell the inventory.
The chain is the third thing. The SupplyChain object inside a bid request records the nodes this transaction actually passed through, appended hop by hop, with the last node being the entity sending the request. It turns the first two layers from static declarations into a checkable record of this particular transaction — which in turn requires that every hop's asi and sid can be found in the files of those two layers. When they cannot, the chain contains an undisclosed party.
This domain is organized by what each standard does, in four layers; both this page and the volume IA follow that axis. The layer definitions come from standards.json and are not restated here:
- AuthorizationPublishers and app developers declare, under a domain they control, which advertising systems and which account IDs are authorized to sell their inventory.
- Identity disclosureAn advertising system discloses, under its own root domain, which legal entities it represents as sellers, their identifiers within its system, and whether each is a direct seller or an intermediary.
- In-request carriageThe bid request carries the node chain this transaction actually traversed, appended hop by hop, with the last node being the entity sending the request.
- Consumption & validationBuyers and verifiers combine the three layers to determine whether an account is authorized, who the seller is, and how many hops the path has.
How the standards were added, year by year
These standards were not designed in one pass: authorization came first, then identity disclosure, and only later did inventory ownership and the exclusive monetization manager become machine-readable. Reading the sequence once settles which version is current and which capability arrived in which release.
Only events whose date is stated in the official document are listed. The app-ads.txt and SupplyChain object specifications carry no version number and no release date anywhere in their text, so neither is placed on the timeline; their status is in the registry below.
Authorization takes shape
The problem was domain spoofing and unauthorized sale. The approach: a publisher places a plain-text file under a domain it controls, listing the advertising systems and account IDs authorized to sell its inventory — the fact that the file can be placed under that domain is itself the proof of the publisher's intent.
- ads.txt 1.0, first version. The record has four fields: the advertising system domain, the publisher account ID, the account relationship type (DIRECT / RESELLER), and an optional certification authority ID· last-verified 2026-10-29
- ads.txt 1.0.1: minor revisions following community feedback, clarifying §3.1 and adding support for the contact and subdomain variables in §3.2, §3.5, §4.4, §4.5 and §5.5· last-verified 2026-10-29
Identity disclosure is added
ads.txt said which account was authorized but not which legal entity stood behind it. sellers.json added that layer: an advertising system publishes the seller entities it represents, their identifiers within its system, and whether each is a direct seller or an intermediary. The same period also brought a standardized way to express an empty file.
- ads.txt 1.0.2: adds §3.2.1 and §4.7, replacing the empty-file method with a placeholder record (placeholder.example.com, placeholder, DIRECT, placeholder) to express the intent of authorizing no advertising system; also separates ads.txt from app-ads.txt in the about section· last-verified 2026-10-29
- sellers.json 1.0, first version. Three objects — Parent, Identifier and Seller — where Seller.seller_type takes PUBLISHER / INTERMEDIARY / BOTH and seller_id is the same value as the ads.txt account ID and the sid of a SupplyChain node· last-verified 2026-10-29
Ownership and management
CTV and in-app inventory sharing made two questions machine-readable necessities: who owns this inventory, and who is the most direct route to buy it. 1.0.3 added inventorypartnerdomain for content-owner authorization; 1.1 added ownerdomain and managerdomain for the owner and the exclusive monetization manager, and tied ads.txt DIRECT / RESELLER values directly to sellers.json.
- ads.txt 1.0.3 final release (public comment December 2020): adds the inventorypartnerdomain directive for CTV-like cases where one entity owns the content and another holds the right to sell the ad space, with details in §4.6 and §5.7· last-verified 2026-10-29
- ads.txt 1.1 final release (public comment April 2022): adds the managerdomain and ownerdomain variables, detailed in §3.5.1, §4.7, §4.8, §5.8 and §5.9. This is the current version ingested on this site· last-verified 2026-10-29
The four layers and how they interlock
The four layers express a division of responsibility; the relation list expresses the constraints within and across them. The core relations in this domain are equality constraints — a value in one place must equal a value in another — so they are given as a list with an official citation per entry rather than drawn as edges that could only say two things are related.
- 1
Authorization
Publishers and app developers declare, under a domain they control, which advertising systems and which account IDs are authorized to sell their inventory.
- Publisher root domain
- App developer website
- Inventory partner domain
- ads.txt record (four fields)
- OWNERDOMAIN variable
- MANAGERDOMAIN variable
- 2
Identity disclosure
An advertising system discloses, under its own root domain, which legal entities it represents as sellers, their identifiers within its system, and whether each is a direct seller or an intermediary.
- Advertising system root domain
- A Seller entry in sellers.json
- 3
In-request carriage
The bid request carries the node chain this transaction actually traversed, appended hop by hop, with the last node being the entity sending the request.
- BidRequest.Source
- A SupplyChainNode
- 4
Consumption & validation
Buyers and verifiers combine the three layers to determine whether an account is authorized, who the seller is, and how many hops the path has.
- Authorized seller verifier
- The buyer (DSP)
Relations between the standards
Every relation carries its official source. An empty source means this site has no traceable citation yet, and is rendered as source pending rather than filled in with a plausible-looking reference.
| From | Relation | To | Note | Source |
|---|---|---|---|---|
| Publisher root domain | authorizes (publisher → record) | ads.txt record (four fields) | A publisher declares, at /ads.txt on its own root domain, the advertising systems and account IDs authorized to sell its inventory; the file must be reachable over HTTP/HTTPS with Content-Type text/plain. | ads.txt v1.1.md §3.1 ACCESS METHOD |
| App developer website | authorizes (publisher → record) | ads.txt record (four fields) | Software distributed through app stores puts the same declaration at /app-ads.txt on the developer's website rather than in the app; the store listing must carry the developer URL and the advertising system must include storeurl in the bid request. | app-ads.txt.md §Solution specification |
| ads.txt record (four fields) | refers (record → a file under another domain) | Publisher root domain | The SUBDOMAIN variable points the crawler at an ads.txt on another subdomain within the same root domain, and the data belongs to that subdomain rather than the current one; only root domains may refer to subdomains, and subdomains must not refer onward. | ads.txt v1.1.md §3.5.1 SUBDOMAIN |
| ads.txt record (four fields) | refers (record → a file under another domain) | Inventory partner domain | INVENTORYPARTNERDOMAIN points at the domain of an entity explicitly authorized to monetize ads within that content; when followed, only the partner's ads.txt is read (not app-ads.txt), and the same directive in the partner's file is not followed — one hop only. | ads.txt v1.1.md §3.5.1 INVENTORYPARTNERDOMAIN, §4.6 |
| Advertising system root domain | discloses (advertising system → seller entry) | A Seller entry in sellers.json | Every advertising system listed in an ads.txt file, and any advertising system referenced from a SupplyChain node, should publish a sellers.json at https://{advertising_system_domain}/sellers.json. | sellers-json.md §Implementation |
| A Seller entry in sellers.json | must match (equality constraint) | ads.txt record (four fields) | Seller.seller_id is the same value as ads.txt record Field #2 (the publisher account ID) and the same value as sid in SupplyChain.nodes; all three must agree for authorization, identity and chain to line up. | sellers-json.md §Sellers.json object: Seller (seller_id) |
| A SupplyChainNode | must match (equality constraint) | ads.txt record (four fields) | A node's asi is the canonical domain of the advertising system and should be the same value used to identify sellers in an ads.txt file; both asi and sid should be the values provided in ads.txt files. | supplychainobject.md §Node Definition, §OpenRTB Object: SupplyChainNode (asi) |
| OWNERDOMAIN variable | must match (equality constraint) | A Seller entry in sellers.json | OWNERDOMAIN should equal sellers.domain in that publisher's entries in the referenced sellers.json files; both must be Public Suffix List + 1, not a full hostname or a URL. | ads.txt v1.1.md §3.5.1 OWNERDOMAIN |
| OWNERDOMAIN variable | must match (equality constraint) | A SupplyChainNode | For a SupplyChain with complete=1, the first node — the one representing the originating publisher — should have a sellers.domain matching OWNERDOMAIN; when OWNERDOMAIN is absent, it is assumed to equal the domain where the ads.txt file was found. | ads.txt v1.1.md §3.5.1 OWNERDOMAIN, §4.7 |
| MANAGERDOMAIN variable | must match (equality constraint) | A SupplyChainNode | For ad opportunities monetized by the manager, the domain listed in MANAGERDOMAIN should also be that of the node representing the originating publisher in a complete supply chain; the value syntax is a PSL+1 domain plus an optional ISO 3166-1 alpha-2 country code, at most one per country, with the global entry carrying no country code. | ads.txt v1.1.md §3.5.1 MANAGERDOMAIN, §4.8 |
| BidRequest.Source | carries (request → chain node) | A SupplyChainNode | Carried at BidRequest.Source.schain in OpenRTB 2.6 and later, BidRequest.Source.ext.schain in 2.5, and BidRequest.ext.schain in 2.4 or prior. | supplychainobject.md §OpenRTB Object: SupplyChain |
| A Seller entry in sellers.json | supersedes | ads.txt record (four fields) | Declaration of certification IDs in ads.txt Field #4 (such as the TAGID) is superseded by the identifiers object in sellers.json, and the spec notes the field may be deprecated in a future version. | ads.txt v1.1.md §3.3 Field #4 |
| Authorized seller verifier | used in combination | App developer website | A verifier reads the developer URL from the store listing and canonicalizes it into an app-ads.txt address: www and m subdomains are dropped, a first-level subdomain is kept and tried first, falling back to the root domain when no file is found. | app-ads.txt.md §Appendix A, §Appendix B |
| The buyer (DSP) | used in combination | A SupplyChainNode | A buyer uses ads.txt, sellers.json and the OpenRTB SupplyChain object together to get a more comprehensive view of the supply chain; adoption of the three is near-full. | Implementation Guidance.md §1. Background |
Current status at a glance
Registration status of the four specifications and the two official guides. Where the official document states no version number or release date, that is recorded as unstated with the evidence boundary spelled out; repository commit dates are not used in place of a release date.
| Standard | Kind | Version | Released | Ingested | Chapter |
|---|---|---|---|---|---|
| ads.txt (Authorized Digital Sellers)vendor/iab-supplychain/ads.txt v1.1.md | Specification | 1.1 | 2022-07 | sections 44 · fields 4 · variables 5 · examples 9 · exampleFiles 14 | ads.txt 1.1 |
| app-ads.txt (Authorized Sellers for Apps)app-ads.txt.md states no version number and no release date anywhere in its text. The repository's first commit for the file (2026-03-25) is when it entered the Supply-Chain-Validation repository, which has nothing to do with the specification's release, so it is not used as a release date.vendor/iab-supplychain/app-ads.txt.md | Specification | No version stated officially | No date stated officially | sections 34 · canonicalizationCases 18 · urlMappingCases 6 | app-ads.txt |
| sellers.jsonvendor/iab-supplychain/sellers-json.md | Specification | 1.0 | July 2019 | sections 13 · objects 3 · fields 16 | sellers.json 1.0 |
| OpenRTB SupplyChain objectsupplychainobject.md carries no version stamp and no release date. Its two mentions of “version 1.0 of the spec / of SupplyChain” are example values for the ver field, not a version declaration for the document. The file was first committed to the repository on 2019-04-11 and last on 2022-03-24; those dates evidence file changes only and are not used as a specification release date.vendor/iab-openrtb3/supplychainobject.md | Specification | No version stated officially | No date stated officially | sections 22 · fields 11 | SupplyChain object |
| ads.txt & app-ads.txt: Guidance for Inventory Sharingvendor/iab-supplychain/Explainer Guide.md | Official guide | — | — | cases 5 | Inventory sharing & implementation guidance |
| Ads.txt Implementation Guidancevendor/iab-supplychain/Implementation Guidance.md | Official guide | — | — | cases 7 · validationRules 28 | Inventory sharing & implementation guidance |
Carriage points in OpenRTB
Where supply chain information sits inside a bid request changes with the OpenRTB version. When investigating legacy traffic, establish which version the counterparty runs first, or the chain will be looked for at the wrong path.
| OpenRTB version | Carriage path |
|---|---|
| 2.6 | BidRequest.Source.schain |
| 2.5 | BidRequest.Source.ext.schain |
| ≤2.4 | BidRequest.ext.schain |
The Source object that carries schain also holds fd, tid and pchain. The standalone specification for pchain is not ingested here, so this site makes no assertion about its semantics or lifecycle status. OpenRTB 2.6 · Source object
An adjacent disclosure signal
The ad-transparency obligations of the EU Digital Services Act (DSA) are carried via regs.ext.dsa on the request side and bid.ext.dsa on the response side. It is a disclosure signal — neither consent nor opt-out. Its specification status, evolution and sources are maintained in one place by the Privacy module; this module does not register them again and only provides the entry point here, so that one fact is not stored in two places where they could contradict each other.
Privacy · DSA transparency →Who owns what
All five standards and guides are published by IAB Tech Lab, but attributed to different working groups and hosted in two different repositories. The licence is declared in each document's header, and the repositories have no root LICENSE file — an inconsistency recorded in the source-defect list.
| Publisher | Owns | Licence |
|---|---|---|
| IAB Tech Lab ↗All five are published by IAB Tech Lab but attributed to different working groups (ads.txt to the Programmatic Supply Chain Working Group, sellers.json to the OpenRTB Working Group), and they are hosted in two different repositories. Neither repository has a LICENSE file. ads.txt, app-ads.txt and sellers.json each declare CC-BY 3.0 in their own header, whereas the two guides and the SupplyChain object specification have no licence section at all and can only be inferred from their repository README — and the CC-BY 3.0 line in the Supply-Chain-Validation README names Ads.txt only. This site records what each document states, does not supply a repository-level licence on the official body's behalf, and does not extend the README's attribution to documents that carry none. |
|
|
Core terms
These are the terms this domain cannot be read without. asi, sid, seller_id in sellers.json and Field #2 of an ads.txt record all denote the same identifier, and OWNERDOMAIN must equal sellers.domain — equality relations of this kind are exactly what a check lands on, and each entry states them.
ads.txtAuthorized Digital Sellers
Authorized Digital Sellers (ads.txt). A plain-text declaration file a publisher or app developer places under its own root domain, listing line by line the advertising system domain authorized to sell its inventory, its own account ID within that system, the account relationship type, and an optional certification authority ID. That the file can be placed under that domain is itself the proof of the publisher's intent; the specification states it was inspired by robots.txt.
ads.txt v1.1.md §1 ABSTRACT, §3 SPECIFICATION
app-ads.txtAuthorized Sellers for Apps
Authorized Sellers for Apps (app-ads.txt). The extension of ads.txt to software distributed through mobile app stores, connected-TV app stores and similar channels. The declaration lives at /app-ads.txt on the developer's website, not inside the app; a verifier reads the developer URL from the store listing and canonicalizes it into that file's address.
app-ads.txt.md §Abstract, §Solution specification
sellers.json
A JSON disclosure file an advertising system places under its own root domain, publishing which legal entities it represents as sellers, their identifiers within its system, and whether each is a direct seller or an intermediary. It lets a buyer discover the identity of the final seller of a bid request and of the entities behind each SupplyChain node.
sellers-json.md §Abstract, §Introduction
SupplyChain objectschain
The SupplyChain object (OpenRTB field name schain) lets a buyer see all parties selling or reselling a given bid request. It is composed of a set of nodes, each representing a specific entity participating in the transacting of inventory; from first to last node it represents every entity involved in the direct flow of payment. Usable as an extension with OpenRTB 2.5, and officially part of the Source object from 2.6 and 3.0.
supplychainobject.md §Abstract, §Implementation
asiadvertising system identifier
The advertising system identifier (asi), a required SupplyChainNode field, is the canonical domain name of the SSP, exchange, header wrapper or similar system that bidders connect to; where the system's operational domain differs from the parent corporate domain it may be used instead, to facilitate WHOIS and reverse-IP lookups establishing ownership. It should be the same value used to identify sellers in an ads.txt file. Only the canonical domain — never a full URL or a scheme prefix.
supplychainobject.md §OpenRTB Object: SupplyChainNode (asi)
sidseller ID
The seller ID (sid), a required SupplyChainNode field, identifies the seller or reseller account within that advertising system and indicates whom the advertising system pays for this inventory. It must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange — typically publisher.id in OpenRTB. It is the same identifier as seller_id in sellers.json and Field #2 of an ads.txt record. A sid must not represent multiple entities, though one entity may hold multiple sids within an advertising system. The spec suggests limiting it to 64 characters.
supplychainobject.md §Node Definition, §OpenRTB Object: SupplyChainNode (sid); sellers-json.md §Sellers.json object: Seller (seller_id)
hp
A required integer field of SupplyChainNode indicating whether this node will be involved in the flow of payment for the inventory. When 1, the advertising system in asi pays the seller in sid, who is responsible for paying the previous node in the chain; when 0, this node is not involved in the payment flow. The spec states that for version 1.0 of SupplyChain this property should always be 1, yet it is explicitly required and must be propagated onward, because future versions are expected to introduce non-payment-handling nodes. Note: the official document never expands the abbreviation hp, and this site does not supply an expansion on the spec's behalf.
supplychainobject.md §OpenRTB Object: SupplyChainNode (hp)
complete
A required integer flag on the SupplyChain object indicating whether the chain contains all nodes involved in the transaction leading back to the owner of the site, app or other medium of the inventory: 0 = no, 1 = yes. An originating request sets it to 1 with only its own node; a reseller of a request that carried no SupplyChain creates the object, sets 0 and inserts its own node; a reseller of a request that already carried one keeps the original complete value and appends its node to the end.
supplychainobject.md §OpenRTB Object: SupplyChain (complete), §Implementation Details
serialization
The string serialization used to convey supply chain information in non-OpenRTB requests (ad tags, VAST URLs, SSAI and similar). The object properties and the node array are separated by a bang; the object property order is ver,complete and the node property order is asi,sid,hp,rid,name,domain,ext. Optional values may be omitted and trailing separators optionally excluded; values containing a comma or a bang must be URL-encoded, while the separating commas are not. The suggested parameter name is schain, with a macro (for example $SCHAIN) emitting the string.
supplychainobject.md §SupplyChain for Non-OpenRTB Requests, §Format of serialization
DIRECT
One of the values of ads.txt record Field #3 (type of account/relationship), indicating that the publisher (content owner) directly controls the account in Field #2 on the system in Field #1 — typically meaning a direct business contract between the publisher and the advertising system. The field is to be treated as case insensitive.
ads.txt v1.1.md §3.3 THE DATA RECORD (Field #3)
RESELLER
The other value of ads.txt record Field #3, indicating that the publisher has authorized another entity to control the account in Field #2 and to resell its ad space via the system in Field #1. The implementation guidance further requires DIRECT / RESELLER to be checked against seller_type in sellers.json.
ads.txt v1.1.md §3.3 THE DATA RECORD (Field #3); Implementation Guidance.md §1. Background
ads.txt record
A single ads.txt data record: four comma-separated fields — Field #1 the canonical domain of the advertising system (required), Field #2 the publisher's account ID within that system (required; typically publisher.id in OpenRTB), Field #3 the account relationship type (required; DIRECT or RESELLER), Field #4 a certification authority ID (optional, e.g. the TAGID). No field may contain tabs, commas or whitespace, otherwise it must be URL-encoded; lines starting with # are comments; extension fields must be preceded by a distinct final separator ";".
ads.txt v1.1.md §3.3 THE DATA RECORD, §3.4 SYNTAX DEFINITION
seller_type
A required enumeration field of the Seller object in sellers.json, taking PUBLISHER, INTERMEDIARY or BOTH. PUBLISHER means the inventory sold through this account sits on a site, app or other medium owned by the named entity and the advertising system pays them directly; INTERMEDIARY means the inventory is not owned by the named entity, or the advertising system does not pay them directly; BOTH means the seller transacts both kinds. Treated as case insensitive.
sellers-json.md §Sellers.json object: Seller (seller_type)
OWNERDOMAIN
A variable added in ads.txt 1.1 giving the business domain of the entity that owns the domain/site/app (e.g. example.com owns example1.com, example2.com). The value should be Public Suffix List + 1 and the same as sellers.domain in that publisher's entries in the referenced sellers.json files. For a complete SupplyChain, the first node representing the originating publisher should have a sellers.domain matching it. If several instances appear only the first is used; it is recommended even when identical to the domain hosting the ads.txt file; when absent, it is assumed to equal the domain being monetized where the file was found.
ads.txt v1.1.md §3.5.1 OWNERDOMAIN, §4.7
MANAGERDOMAIN
A variable added in ads.txt 1.1 giving the business domain of a primary or exclusive monetization partner for the publisher's inventory. Value syntax: a PSL+1 domain (required) plus an ISO 3166-1 alpha-2 country code (optional, blank meaning global). It is to be used only for a party that is not the publisher but is the primary or exclusive programmatic seller for the site, typically only where the publisher does not sell its own inventory in that market. Multiple values are allowed but only one per country; the global default carries no country extension and can be overridden by entries that do. For opportunities monetized by the manager, this domain should also be that of the node representing the originating publisher in a complete supply chain.
ads.txt v1.1.md §3.5.1 MANAGERDOMAIN, §4.8; Implementation Guidance.md §1. Background
root domainPSL+1
The root domain, defined by all three specifications in the same sentence as the public suffix plus one string in the name — Public Suffix List + 1 (PSL+1). ads.txt, app-ads.txt and sellers.json impose the same requirement on domains: asi, domain and OWNERDOMAIN carry PSL+1 only, never a full hostname or URL, and crawlers should incorporate the Public Suffix List to derive the root domain. Valid forms include example.com and example.co.uk; invalid forms include http://example.com and https://example.com/about-us.html.
ads.txt v1.1.md §3.1; sellers-json.md §ACCESS METHOD, §Sellers.json object: Seller; supplychainobject.md §OpenRTB Object: SupplyChainNode
SPOSupply Path Optimization
Supply Path Optimization (SPO). Buyers prefer to minimize the number of hops taken to purchase a piece of inventory, which requires identifying a primary or exclusive monetization partner — the reason MANAGERDOMAIN was introduced: even where the supply path has multiple hops, going through the manager may still be the most direct route. The implementation guidance lists accurately representing seller relationships and introducing the concept of primary or exclusive sellers among the SPO needs this update addresses.
Implementation Guidance.md §1. Background, §2. Scope; ads.txt v1.1.md §3.5.1 MANAGERDOMAIN
inventory sharing
Inventory sharing: some business entity other than the app or site owner holds ownership of, and the right to sell, some ad space within that app or site. It occurs far more often in connected TV and OTT, typically arising from content distribution (MVPD or vMVPD) or carriage agreements (TV Everywhere). The official scope explicitly includes inventory sharing but excludes revenue sharing, where ownership and sale of the ad inventory remain with a single entity that merely shares ad revenue back with content owners.
Explainer Guide.md §Background, §Scope (In Scope / Out of Scope)
Suggested reading path
To understand the domain systematically, read in this order: establish the record model of the authorization declaration, add identity disclosure, then look at the in-request chain object and its string form, and finally use the official CASE walkthroughs to tie the three together.
- 1ads.txt 1.1: the four record fields, the five variables and the nine official examples
- 2sellers.json: the Parent / Identifier / Seller objects and the seller_type enumeration
- 3The SupplyChain object: node definition, carriage paths and the construction rules on resale
- 4URL serialization for non-OpenRTB requests, with the six official paired examples
- 5Implementation guidance CASE A–G: the five-column walkthrough of bid request, ads.txt, sellers.json, validation and answer
- 6The Source object in OpenRTB 2.6: where schain is carried in a request