Volume navigation
Inventory sharing & implementation guidance
No version stated officiallyOn this page
- What this chapter covers
- Key facts
- Defects in the official source
- Structured highlights
- Official text
- Background
- In Scope
- Out of Scope
- Updates to Ads.txt & App-Ads.txt Standard
- Example Use Cases
- CASE A: Programmer Owned App
- CASE B: Content Channel on vMVPD app
- Business Scenario B.1
- Business Scenario B.2
- CASE C: Programmer Owned App using MVPD sign-in (TV Everywhere)
- Use Case Implementation Logic
- CTV App Store Guidance
- Publisher Guidance
- SSP/Exchange Guidance
- DSP Guidance
- 1. Background
- 2 Scope
- In Scope
- Out of Scope
- 3 Updates to Ads.txt & App-Ads.txt Standard
- 4 Example Use Cases
- Definitions:
- CASE A: Publisher inhouse monetization
- CASE B: Publisher managed monetization
- CASE C: Publisher managed monetization; country specific
- CASE D: Publisher inhouse monetization for proprietary placement type
- CASE E: Resale of publisher inhouse monetization for proprietary placement type
- CASE F: owned inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
- CASE G: Resold inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
- 5 Implementation Guidelines
- Publisher Guidance
- SSP/Exchange Guidance
- DSP Guidance
- Related chapters
- Sources
What this chapter covers
The two official guides: the inventory-sharing guide covers CTV / vMVPD cases where several entities hold rights to sell ad space within one app (CASE A, B.1, B.2, C), and the implementation guidance ties ads.txt DIRECT / RESELLER values directly to sellers.json, with seven CASEs laid out in five columns (bid request, ads.txt, sellers.json, validation, answer).
- Background and scope: inventory sharing in scope, revenue sharing out of scope
- Updates to the ads.txt and app-ads.txt standards
- Facts and file contents of inventory-sharing CASE A, B.1, B.2, C
- The five-column walkthrough of implementation CASE A–G
- The interlock rules in the Validation column (the source of this site's relation list)
- Implementation guidelines for publishers, exchanges and DSPs
Key facts
- Version
- No version stated officially · No version stated officially
- Released
- No date stated officially · No date stated officially
- Official source file
- Explainer Guide.md · Implementation Guidance.md
- sha256
- 6a036746d233 · fe92b8850fa8
- Baseline commit
- 7682963ae241
- Fetched
- 2026-10-29
- Ingested
- cases 5 · cases 7 · validationRules 28
Defects in the official source
Defects found in the official document while ingesting this chapter, with line-level evidence. Nothing is repaired: the samples rendered on this page stay exactly as the official source has them.
Implementation Guidance.md · the CASE A–G diagrams
stale image pathAll 7 CASE diagrams link to the pre-rename ads.txt-app-ads.txt repository, each pinned to a different historical commit (7 distinct commits). GitHub 301-redirects renamed repositories so the links do not break, but both the path names and the commits are stale. The Explainer Guide contains no diagrams at all. This site records the official URLs as-is and does not mirror them into public/ — the same handling as the SIMID module.
vendor/iab-supplychain/Implementation Guidance.md:60 · vendor/iab-supplychain/Implementation Guidance.md:149 · vendor/iab-supplychain/Implementation Guidance.md:255 · vendor/iab-supplychain/Implementation Guidance.md:376 · vendor/iab-supplychain/Implementation Guidance.md:470 · vendor/iab-supplychain/Implementation Guidance.md:588 · vendor/iab-supplychain/Implementation Guidance.md:679
Implementation Guidance.md · the Validation column of CASE A–G
inconsistent wordingThe Validation column of all seven CASEs states the same four rules (the equality and inequality branches of sellers.domain against OWNERDOMAIN / MANAGERDOMAIN / MANAGERDOMAIN+GEO), but the official wording is not uniform: the domain placeholder is A=publisher.com B=publisher.com C=publisher.com D=site.com E=site.com F=publisher.com G=publisher.com, and the fourth conclusion in CASE E stops at "THEN seller is reseller", omitting the "of inventory" the other six have. This site normalizes the rules by shape into a single source, records the wording differences as they are, and does not harmonize the official wording on its behalf.
vendor/iab-supplychain/Implementation Guidance.md:120-135 · vendor/iab-supplychain/Implementation Guidance.md:441-456 · vendor/iab-supplychain/Implementation Guidance.md:558-573
Structured highlights
Interlock rules
The same four rules the official guide repeats in the Validation column of all seven CASEs: the equality and inequality branches of sellers.domain against OWNERDOMAIN and MANAGERDOMAIN. The wording is not uniform across the seven (the domain placeholder is publisher.com in some and site.com in others, and CASE E's fourth rule omits of inventory), so they are normalized here by rule shape into one list showing which CASEs state each, with the wording differences logged as a defect.
| Condition | Conclusion | Stated in |
|---|---|---|
| sellers.domain = OWNERDOMAIN | seller is owner of publisher.com | CASE A · CASE B · CASE C · CASE D · CASE E · CASE F · CASE G |
| sellers.domain = MANAGERDOMAIN | seller is manager of publisher.com | CASE A · CASE B · CASE C · CASE D · CASE E · CASE F · CASE G |
| sellers.domain = MANAGERDOMAIN + GEO | seller is manager of publisher.com for GEO | CASE A · CASE B · CASE C · CASE D · CASE E · CASE F · CASE G |
| sellers.domain != OWNERDOMAIN or MANAGERDOMAIN | seller is reseller of inventory | CASE A · CASE B · CASE C · CASE D · CASE E · CASE F · CASE G |
- Official wordingIF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com
- Official wordingIF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com
- Official wordingIF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO
- Official wordingIF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventory
Inventory sharing CASEs (Explainer Guide)
The four situations in CTV and vMVPD contexts where several entities hold rights to sell ad space within one app. The official guide expresses them as bold-labelled fact lists rather than tables.
CASE AProgrammer Owned App
Business scenarioAll of the inventory is being produced and sold by programmer A, in their owned app, via their chosen SSPs. This is the most straightforward example of OTT inventory and does not differ from the current app-ads.txt authorization model.
- App
- Programmer A App (app bundle ID: 12345)
- Developer URL domain for the app
- devsite.programmerA.com
- Seller/Publisher
- Programmer A (publisher ID: abcde)
- Content Producer
- Programmer A
Declaration files
Programmer A app-ads.txt file · devsite.programmerA.com/app-ads.txt
ssp.com, abcde, DIRECT, *OpenRTB declaration
{ "app": { "bundle": "12345", "storeurl": "https://ctvappstore.com/details/12345/programmerA", "publisher": { "id": "abcde" }, } }- The “Certification Authority ID” field may also be included in ads.txt & app-ads.txt files, but is omitted from these examples as it is optional.*
CASE BContent Channel on vMVPD app
In this case, we will present two different ways that authorization for ads running against licensed content appearing inside a vMVPD app may appear in bid requests and app-ads.txt & ads.txt files. These are presented as Business Scenarios B.1 and B.2.
CASE B.1Business Scenario B.1
vMVPD B has rights to sell the ad slot, the ad is served into Programmer A’s content within the vMVPD B app. Information about the content ownership (i.e., the content is owned by Programmer A) is “blinded” - not declared in the bid request. This is similar to Case A (app owner selling inventory on their app w/o specific content declaration) and does not differ from the current app-ads.txt authorization model.
- App
- vMVPD B App (app bundle ID: 67890)
- Developer URL domain for the app
- devsite.vMVPDB.com
- Seller/Publisher
- vMVPD B (publisher ID: vwxyz)
- Content Producer
- Programmer A
Declaration files
vMVPD B app-ads.txt file · devsite.vMVPDB.com/app-ads.txt
ssp.com, vwxyz, DIRECTOpenRTB declaration
{ "app": { "bundle": "67890", "storeurl": "https://ctvappstore.com/details/67890/vmvpdB", "publisher": { "id": "vwxyz" }, } }CASE B.2Business Scenario B.2
Programmer A has rights to sell the ad slot, the ad served into Programmer A content within the vMVPD B app.
- App
- vMVPD B App (app bundle ID: 67890)
- Developer URL domain for the app
- devsite.vMVPDB.com
- Seller/Publisher
- Programmer A (publisher ID: abcde)
- Content Producer
- Programmer A
Declaration files
vMVPD B app-ads.txt file · devsite.vMVPDB.com/app-ads.txt
ssp.com, vwxyz, DIRECT inventorypartnerdomain=programmerA.comOpenRTB declaration
{ "app": { "bundle": "67890", "storeurl": "https://ctvappstore.com/details/67890/vmvpdB", "inventorypartnerdomain": "programmerA.com”, "publisher": { "id": "abcde" } } }- *Programmer A ads.txt file* (programmerA.com/ads.txt):
- ssp.com, abcde, DIRECT
CASE CProgrammer Owned App using MVPD sign-in (TV Everywhere)
Business scenarioDue to the user login to programmer A’s app with the vMVPD B’s login credentials, vMVPD B has rights to sell the ad slot within programmer A’s app. Note this is the reverse of Case B: Business scenario 2.
- App
- Programmer A App (app bundle ID: 12345)
- Developer URL domain for the app
- devsite.programmerA.com
- Seller/Publisher
- vMVPD B (publisher ID: vwxyz)
- Content Producer
- Programmer A
Declaration files
vMVPD B ads.txt file · vMVPDB.com/ads.txt
ssp.com, vwxyz, DIRECT- *Programmer A app-ads.txt file* (devsite.programmerA.com/app-ads.txt):
Implementation guidance CASE A–G
Each CASE lays one transaction out in five columns: what the bid request looks like, how the publisher's ads.txt is written, how the advertising system's sellers.json is written, by what rule it is validated, and what the answer is.
CASE APublisher inhouse monetization
Business scenarioThe publisher monetizes their inventory internally. They operate the seats on the exchanges: Publisher.com is the business entity that owns site.com
Supply pathPublisher -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placecment on site.com sold by exchange.com (sid 1234) "site.domain" : "site.com" "publisher.id" : "1234" "schain" : { "nodes": [ { "sid" : "1234", "asi" : "exchange.com" } ] }site.com/ads.txt OWNERDOMAIN = publisher.com exchange.com, 1234, DIRECTexchange.com/sellers.json { "seller_id" : "1234", "name" : "Publisher", "domain" : "publisher.com", "seller_type" : "Publisher" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1234 is owner of site.com and DIRECT path of inventory CASE BPublisher managed monetization
Business scenarioThis case represents the publisher monetizing their inventory through an exclusive monetization partner. While the supply path includes multiple hops, it is still the most direct route from a Supply Path Optimization perspective to purchase the inventory.
Supply pathPublisher -> Manager -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by manager.com (sid 5678) through exchange.com (sid 1235) "site.domain" : "site.com" "publisher.id" : "1235" "schain" : { "nodes": [ { "sid" : "5678", "asi" : "manager.com" }, { "sid" : "1235", "asi" : "ecxhange.com" } ] }site.com/ads.txt OWNERDOMAIN = publisher.com MANAGERDOMAIN = manager.com manager.com, 5678, DIRECT exchange.com, 1235, RESELLERmanager.com/sellers.json { "seller_id" : "5678", "name" : "Publisher", "domain" : "publisher.com", "seller_type" : "Publisher" } exchange.com/sellers.jso n { "seller_id" : "1235", "name" : "Manager", "domain" : "manager.com", "seller_type" : "Intermediary" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1235 is the monetization Mapager of site.com and is the most DIRECT path to inventory. Seller 5678 is the owner of site.com which has a DIRECT relationship with Manager CASE CPublisher managed monetization; country specific
Business scenarioThis case represents the publisher monetizing their inventory through an exclusive monetization partner in a specific country. While the supply path includes multiple hops, it is still the most direct route from a Supply Path Optimization perspective to purchase the inventory.
Supply pathPublisher -> Manager + GEO -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by saleshouseDE.com (sid 9876) through exchange.com (sid 1236) "site.domain" : "site.com" "publisher.id" : "1236" "schain" : { "nodes": [ { "sid" : "9876", "asi" : "saleshouseDE.com" }, { "sid" : "1236", "asi" : "ecxhange.com" } ] }site.com/ads.txt OWNERDOMAIN = publisher.com MANAGERDOMAIN = saleshouseDE.com, DE salehouseDE.com, 9876, DIRECT exchange.com, 1236, RESELLERsaleshouseDE.com/sellers.json { "seller_id" : "9876", "name" : "Publisher", "domain" : "publisher.com", "seller_type " : "Publisher" } exchange.com/seller s.json { "seller_id" : "1236", "name" : "Salehouse DE", "domain" : "saleshouseDE.com" , "seller_type " : "Intermediary" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1236 is the monetization manager of site.com for DE only and is the most DIRECT path to inventory. Seller 9786 is the owner of site.com which has a DIRECT relationship with Saleshouse DE CASE DPublisher inhouse monetization for proprietary placement type
Business scenarioThe publisher monetizes their inventory internally. They operate the seat with the proprietary placement type directly. Publisher -> Proprietary Placement -> DSP
Supply pathPublisher -> Proprietary Placement -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by proprietaryplacement.com (sid 45678) "site.domain" : "site.com" "publisher.id" : "45678" "schain" : { "nodes": [ { "sid" : "45678", "asi" : "proprietaryplacemen t.com" } ] }site.com/ads.txt OWNERDOMAIN = publisher.com MANAGERDOMAIN = manager.com manager.com, 5678, DIRECT exchange.com, 1235, RESELLER proprietaryplacement. com, 45678, DIRECTproprietaryplacement.com/sellers.json { "seller_id" : "45678", "name" : "Publisher", "domain" : "publisher.com", "seller_type " : "Publisher" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of site.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of site.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of site.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 45678 is the owner of site.com and DIRECT path to proprietary placement inventory. CASE EResale of publisher inhouse monetization for proprietary placement type
Business scenarioThe publisher monetizes their inventory internally. They operate the seat with the proprietary placement type directly. The proprietary placement vendor then sells the inventory on an exchange.
Supply pathPublisher -> Proprietary Placement -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by proprietaryplacement.c om (sid 45678) through exchange.com (sid 1238) "site.domain" : "site.com" "publisher.id" : "1238" "schain" : { "nodes": [ { "sid" : "45678", "asi" : "proprietarypla cement.com" }, { "sid" : "1238", "asi" : "exchange.com " } ] }site.com/ads.txt OWNERDOMAIN = publisher.com MANAGERDOMAIN = manager.com manager.com, 5678, DIRECT exchange.com, 1235, RESELLER proprietaryplacement.com, 45678, DIRECT exchange.com, 1238, RESELLERproprietaryplacement.com/sellers.json { "seller_id" : "45678", "name" : "Publisher", "domain" : "publisher.com", "seller_type" : "Publisher" } exchange.com/sellers.json { "seller_id" : "1238", "name" : "Proprietary Placement", "domain" : "proprietaryplacem ent.com", "seller_type" : "Intermediary" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of site.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of site.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of site.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1238 is not the owner or manager of site.com and is a reseller path to underlying inventory. Seller 45678 is the owner of site.com and Proprietary Placement is a DIRECT path to the underlying inventory. CASE Fowned inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
Business scenarioThe entity selling the inventory is both a media owner and a monetization manager for different pieces of inventory. The below illustrates what would be expected for a piece of inventory that is owned by the entity.
Supply pathPublisher -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by exchange.com (sid 1240) "site.domain" : "site.com" "publisher.id" : "1240" "schain" : { "nodes": [ { "sid" : "1240", "asi" : "ecxhange.co m" } ] }site.com/ads.txt OWNERDOMAIN = xyzmedia.com exchange.com, 1240, DIRECTexchange.com/sellers.json { "seller_id" "1240", "name" : "XYZ Media", "domain" : "xyzmedia.c om", "seller_type " : "Both" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1240 is owner of site.com and DIRECT path to inventory CASE GResold inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
Business scenarioThe entity selling the inventory is both a media owner and a monetization manager for different pieces of inventory. The below illustrates what would be expected for a piece of inventory that is being sold by the entity on behalf of another publisher.
Supply pathPublisher -> Manager -> Exchange -> DSP

Bid Request Publisher's Authorized Sellers (Ads.txt) Sellers.json Validation Answer DSP receives a bid request for a placement on site.com sold by xyzmedia.com (sid xyz) through exchange.com (sid 1240) "site.domain" : "site.com" "publisher.id" : "1240" "schain" : { "nodes": [ { "sid" : "123xyz", "asi" : "ecxhange.co m" }, { "sid" : "1240", "asi" : "ecxhange.com" } ] }site.com/ads.txt OWNERDOMAIN = publisher.com xyzmedia.com, 123xyz, DIRECT exchange.com, 1240, RESELLERxyzmedia.com/sellers.json { "seller_id" : "123xyz", "name" : "Publisher", "domain" : "publisher.com", "seller_type" : "Publisher" } exchange.com/sellers .json { "seller_id" : "1240", "name" : "XYZ Media", "domain" : "xyzmedia.com", "seller_type" : "Both" }IF sellers.domain = OWNERDOMAIN THEN seller is owner of publisher.com IF sellers.domain = MANAGERDOMAIN THEN seller is manager of publisher.com IF sellers.domain = MANAGERDOMAIN + GEO THEN seller is manager of publisher.com for GEO IF sellers.domain != OWNERDOMAIN or MANAGERDOMAIN THEN seller is reseller of inventorySeller 1240 is not the owner or manager of site.com and is a RESELLER path to underlying inventory. Seller 123xyz is the owner of site.com and ZYZ Media is a DIRECT path to the underlying inventory.
Official text
The text below is recorded in the order of the official document, not rewritten, not added to and not translated. Section numbers and titles are the official ones, and the anchors follow the official slug rule.
Explainer Guide.md
Background
The Connected TV market introduces a much higher occurrence of complex monetization relationships that make ads.txt & app-ads.txt, as currently designed, insufficient for broader adoption. (*It is important to note that these relationships are not unique to the CTV environment or OTT content delivery, however, the much higher occurrence of these relationships in CTV/OTT contexts rendered this problem in particular need of resolution.*) These guidelines & spec enhancements are intended to more seamlessly support site & apps in which multiple entities may have ownership rights over the ad space, commonly referred to as “inventory sharing”. In OTT, these situations often arise from relationships such as content distribution (MVPDs or vMVPDs) or as a result of various carriage agreements (TV Everywhere). Ultimately, nearly all relationships can be simplified into the case where “some business entity, other than the app/site owner, has ownership over some ad space within the app/site and the right to sell that inventory.”
A simple example of one such situation is a content distributor such as a vMVPD app. In these content distribution agreements, one entity, a content producer/programmer A, gives rights to a content distributor B, to rebroadcast their content. As part of the agreement, both A & B have ownership of some portion of ad inventory delivered into the streamed content (the inventory is “shared”). By using the word “ownership”, we imply that both A & B may legitimately originate an ad request inside an app that will be propagated into the programmatic ecosystem.
In the current ads.txt & app-ads.txt standard, declaring this relationship would require the vMVPD app to authorize Programmer A in their app-ads.txt file, along with the programmers’ authorized seller and reseller information. This increases the cost of generating and maintaining an app-ads.txt file, and incrementally decreases the security benefit of the standard as the number of authorized sellers grows.
It is these scenarios that we intend to define and validate via the Ads.txt & App-ads.txt for Inventory Sharing guidelines for CTV/OTT.
In Scope
Business relationships: This solution covers inventory sharing relationships, where different entities (app/site owner, content owner) may have the right to sell ad space within a piece of content on a given app/site.
Potential abuse vectors: This solution is intended to address basic misrepresentations of publishers’ ownership of (and rights to sell) inventory on an app/site; answering the question:
*“Does publisher A have ownership of (and rights to sell) some inventory on app/site B?”*
Out of Scope
Business relationships: This solution does not cover revenue sharing scenarios, where one entity owns & sells the ad inventory associated with content provided by a content owner (e.g., YouTube, DailyMotion). The owning entity may share revenue generated from ad sales back with the content owners, but ultimately there is only one entity owning/selling the ad inventory.
Potential abuse vectors: This solution does not address additional aspects of content rights ownership or media rights management such as exclusivity or inventory ownership within specific content/shows. We are not attempting to answer questions:
*“Does publisher A have rights to sell inventory within this specific TV show or programming?”*
OR:
*“Does app/site C have the exclusive rights to deliver/stream a specific TV show or programming?”*
While these concepts are increasingly important, especially in the space of Connected TV and OTT streaming, they will require new solutions being developed.
Updates to Ads.txt & App-Ads.txt Standard
In the previous version of ads.txt & app-ads.txt, supporting these scenarios would have required the app/site owner/developer to maintain their ads.txt/app-ads.txt file with the publisher IDs of all the partners (and their resellers) with whom they have negotiated some share of inventory ownership rights - making many ads.txt/app-ads.txt files prohibitively difficult to maintain. Note that moving to this method means that the publisher accepts all entries in the partner’s ads.txt/app-ads.txt file as authorized to sell their inventory and assumes the risk of any changes to that file with or without their knowledge.
Instead, the ads.txt & app-ads.txt specs have been updated to include the ability to designate another domain (aside from the app/site developer’s) that is able to validate the publisher ID of the bid request. These domains are to be passed through site and app objects in the OpenRTB spec:
- *app.inventorypartnerdomain*
OR
- *site.inventorypartnerdomain*
To validate these domains, the (app)ads.txt spec also includes the following additional declaration in ads.txt & app-ads.txt files (defined in ads.txt), intended to be entered by the owner of the app/site:
| VARIABLE | VALUE | DESCRIPTION |
|---|---|---|
| inventorypartnerdomain | Pointer to the domain of the partner (of the site/app owner) with ownership of some portion of ad inventory on the site/app. The partner’s ads.txt or appads.txt file will be hosted here. | When a site or an app contains ad inventory that is owned by another partner - the app or site should list all domains for those partners via this directive. |
Please see the example use cases later in this document for how these values work together to validate inventory in the new version of app-ads.txt.
Example Use Cases
Definitions::
- Programmer A: Content owner or content developer - ex: ESPN, CBS, NBC, Crackle, Tastemade, Sky (UK), TF1 (FR), RTL (DE and NL), SBS (AU), Channel 9 (AU), Nippon TV (JP), etc.
- (v)MVPD: (virtual) Multichannel Video Programming Distributor / Content distributor (monetizing partner, doesn’t always have ownership over user-facing content) - Sling TV, Pluto TV, YouTube TV, The Roku Channel, Fubo, Comcast, Sky (UK), Virgin Media (UK), Orange Télécom (FR) and Bouygues Télécom (FR), Foxtel (AU)
CASE A: Programmer Owned App
Business scenario: All of the inventory is being produced and sold by programmer A, in their owned app, via their chosen SSPs. This is the most straightforward example of OTT inventory and does not differ from the current app-ads.txt authorization model.
App: Programmer A App (app bundle ID: 12345)
Developer URL domain for the app: devsite.programmerA.com
Seller/Publisher: Programmer A (publisher ID: abcde)
Content Producer: Programmer A
OpenRTB Declaration::
{
"app": {
"bundle": "12345",
"storeurl": "https://ctvappstore.com/details/12345/programmerA",
"publisher": {
"id": "abcde"
},
} }Programmer A app-ads.txt file: (devsite.programmerA.com/app-ads.txt):
ssp.com, abcde, DIRECT, *
Note: The “Certification Authority ID” field may also be included in ads.txt & app-ads.txt files, but is omitted from these examples as it is optional.*
CASE B: Content Channel on vMVPD app
In this case, we will present two different ways that authorization for ads running against licensed content appearing inside a vMVPD app may appear in bid requests and app-ads.txt & ads.txt files. These are presented as Business Scenarios B.1 and B.2.
Business Scenario B.1
vMVPD B has rights to sell the ad slot, the ad is served into Programmer A’s content within the vMVPD B app. Information about the content ownership (i.e., the content is owned by Programmer A) is “blinded” - not declared in the bid request. This is similar to Case A (app owner selling inventory on their app w/o specific content declaration) and does not differ from the current app-ads.txt authorization model.
App: vMVPD B App (app bundle ID: 67890)
Developer URL domain for the app: devsite.vMVPDB.com
Seller/Publisher: vMVPD B (publisher ID: vwxyz)
Content Producer: Programmer A
OpenRTB Declaration: (by vMVPD B):
{
"app": {
"bundle": "67890",
"storeurl": "https://ctvappstore.com/details/67890/vmvpdB",
"publisher": {
"id": "vwxyz"
},
}
}vMVPD B app-ads.txt file: (devsite.vMVPDB.com/app-ads.txt): ssp.com, vwxyz, DIRECT
Business Scenario B.2
Programmer A has rights to sell the ad slot, the ad served into Programmer A content within the vMVPD B app.
App: vMVPD B App (app bundle ID: 67890)
Developer URL domain for the app: devsite.vMVPDB.com
Seller/Publisher: Programmer A (publisher ID: abcde)
Content Producer: Programmer A
OpenRTB Declaration: (by Programmer A):
{
"app": {
"bundle": "67890",
"storeurl": "https://ctvappstore.com/details/67890/vmvpdB",
"inventorypartnerdomain": "programmerA.com”,
"publisher": {
"id": "abcde"
}
}
}vMVPD B app-ads.txt file: (devsite.vMVPDB.com/app-ads.txt):
ssp.com, vwxyz, DIRECT
inventorypartnerdomain=programmerA.com*Programmer A ads.txt file* (programmerA.com/ads.txt):
ssp.com, abcde, DIRECT
CASE C: Programmer Owned App using MVPD sign-in (TV Everywhere)
App: Programmer A App (app bundle ID: 12345)
Developer URL domain for the app: devsite.programmerA.com
Seller/Publisher: vMVPD B (publisher ID: vwxyz)
Content Producer: Programmer A
Business scenario: Due to the user login to programmer A’s app with the vMVPD B’s login credentials, vMVPD B has rights to sell the ad slot within programmer A’s app. Note this is the reverse of Case B: Business scenario 2.
{
"app": {
"bundle": "12345",
"storeurl": "https://ctvappstore.com/details/12345/programmerA",
"inventorypartnerdomain": "vmvpdB.com”,
"publisher": {
"id": "vwxyz"
}
}
}*Programmer A app-ads.txt file* (devsite.programmerA.com/app-ads.txt):
ssp.com, abcde, DIRECT
inventorypartnerdomain=vmvpdB.comvMVPD B ads.txt file: (vMVPDB.com/ads.txt):
ssp.com, vwxyz, DIRECT
Use Case Implementation Logic
| Scenario | Do this.. | Possible outcomes |
|---|---|---|
| Bid request is app*, and does not have $.app.inventorypartnerdomain (Corresponds to business use case A, B.1) | Attempt lookup of app-ads.txt @ developer domain retrieved from app store record for $.app.bundle | No valid app-ads.txt records found because store record cannot be found, there is no domain available in store record, the domain does not have an app-ads.txt file, the web server returns an error, etc. -> Nonparticipating inventory, Valid app-ads.txt file is found & bid request publisher ID + advertising system is not found in file -> Unauthorized inventory, Valid app-ads.txt file is found & bid request publisher ID + advertising system is found in file -> Authorized inventory |
| Bid request is app*, and has $.app.inventorypartnerdomain (Corresponds to business use cases B.2, C) | Attempt lookup of app-ads.txt @ developer domain retrieved from app store record for $.app.bundle Attempt lookup of ads.txt @ domain from $.app.inventorypartnerdomain field from bid request | No valid app-ads.txt records found because store record cannot be found, there is no domain available in store record, the domain does not have an app-ads.txt file, the web server returns an error, etc. -> Inconclusive: authorization cannot be determined, IF: Valid app-ads.txt file is found & bid request publisher ID + advertising system is found in app-ads.txt file -> Authorized inventory, ELSE: Valid app-ads.txt file is found & app-ads.txt file does not contain an inventorypartnerdomain directive matching the domain from $.app.inventorypartnerdomain from the bid request -> Unauthorized inventory, App-ads.txt file contains inventorypartnerdomain directive matching the domain from $.app.inventorypartnerdomain from the bid request, but no valid ads.txt records found in the ads.txt file at inventorypartnerdomain because domain does not have an ads.txt file, web server returns an error, etc. -> Inconclusive: authorization cannot be determined, App-ads.txt file contains inventorypartnerdomain directive matching the domain from $.app.inventorypartnerdomain from the bid request, bid request publisher ID + advertising system is not found in inventorypartnerdomain’s ads.txt file -> Unauthorized inventory, App-ads.txt file contains inventorypartnerdomain directive matching the domain from $.app.inventorypartnerdomain from the bid request, bid request publisher ID + advertising system is found in inventorypartnerdomain’s ads.txt file -> Authorized inventory |
*Note: If bid request is site, instead of app, same logic applies but look for $.site.inventorypartnerdomain*
CTV App Store Guidance
Required::
- To ensure the app-ads.txt information is verifiable across ad tech platforms, it is important to make the app store website publicly available on the web.
- CTV app stores are required to support the OTT/CTV Store Assigned App Identification Guidelines by ensuring their store assigned IDs are publicly accessible from their store.
- CTV app stores are required to follow the app-ads.txt standard to add meta tags into the HTML page to publish the developer website URL, bundle id, and store id. The IAB Tech Lab’s demystifying app-ads.txt guidance also defines other methods to publish a publisher’s website URL, bundle id, and store id.
Publisher Guidance
Required::
- Before publishers can adopt app-ads.txt for CTV inventory, they need to adopt the OTT/CTV Store Assigned App Identification Guidelines. Per these guidelines, publishers are required to:
a. Pass CTV app store assigned IDs in the app.bundle field of OpenRTB 2.5 or the app.storeid field of OpenRTB 3.0/AdCOM 1.0.
b. Pass the store URL of the originating app in app.storeurl field of OpenRTB 2.5 and OpenRTB 3.0/AdCOM 1.0.
- App owners should publish their app-ads.txt file on their developer web site, following the app-ads.txt standard. If publishers have already published the app-ads.txt for mobile app inventory, and there are different authorized seller IDs for their CTV app, they should publish a CTV specific app-ads.txt file at a new domain specific for CTV app inventory.
- In addition, App Owners should declare within their app-ads.txt file the domain of Inventory Partners who own inventory within the App Owner’s app using the *inventorypartnerdomain* directive. This should be the domain where the Inventory Partner hosts their ads.txt or appads.txt file.
Note: If an app owner would prefer to list inventory partners seller & reseller IDs directly within the app-ads.txt file, rather than leveraging the inventorypartnerdomain directive, this is also supported.*
Guidance for app publishers passing additional information in bundle fields:
It has been observed that many CTV app publishers are passing additional information in the bundle ID that may be “lost” as part of this transition. Below is guidance on where this information is more appropriately passed:
a. Channel or Network within an app: content.producer.name
b. VOD vs. Livestream: pass in content.livestream
c. Device make/model: pass in device.make & device.model
d. App store: pass in app.storeurl - (*Note: this is already required per the app-ads.txt standard*)
Also see: OTT/CTV User Agent Guidelines
SSP/Exchange Guidance
Required::
- SSPs/Exchanges are required to implement the *app.inventorypartnerdomain* & *site.inventorypartnerdomain* fields from the site and app objects to support the passing of inventory partner domains for pointers to partner ads.txt files, where an inventory partner exists.
- SSPs/Exchanges should support publishers in providing CTV App IDs according to the OTT/CTV Store Assigned App Identification Guidelines* as well as assist them in passing additional contextual & environment signals (as noted in Publisher Guidance section) via the appropriate existing or extension OpenRTB fields.
Failure to comply with the guidelines will prevent the DSP from verifying the app-ads.txt information.*
DSP Guidance
Required::
- DSPs should implement their app-ads.txt crawler according to standardized guidance from CTV app stores (or use a service that adheres to those guidelines).
Implementation Guidance.md
1. Background
Since its introduction in 2017, Authorized Digital Sellers (Ads.txt) has been a successful tool in helping the programmatic ecosystem reduce fraud, specifically misrepresentation (aka “domain spoofing”), and unauthorized sale of ad inventory. With the later creation of sellers.json and the SupplyChain Object, additional disclosure of sellers has furthered transparency throughout the supply chain. At near-full adoption of these specifications, the capability now exists for buyers to use ads.txt, sellers.json, and OpenRTB SupplyChain together to have a more comprehensive view of the supply chain.
However, with different implementation needs and interpretations of the specifications for publishers, ad supply management companies, and SSPs/ad exchanges, challenges have emerged related to the representation of supply through ads.txt. This proposal is meant to evolve ads.txt to maintain its strength in fraud-reduction, increase transparency in seller relationships via sellers.json, and bridge the specification into the larger suite of supply chain transparency standards.
Specifically, this update addresses the following challenges and opportunities for improvement:
- Representing seller relationships accurately: Addressing the needs of Supply Path Optimization (SPO) by linking ads.txt/app-ads.txt directly to sellers.json, to ensure that ads.txt files DIRECT/RESELLER values are accurately described.
- Introducing the concept of primary or exclusive sellers of inventory: Buyers have expressed an interest in minimizing the ‘number of hops’ to purchase a piece of inventory. In cases where a publisher outsources the majority of their monetization, the most direct route may be through a reseller. The updates develop a way, through MANAGERDOMAIN, for ad management firms and sale houses to be identified as primary, or exclusive representatives of a publisher’s inventory.
- Understanding ownership for domains/apps: To better connect the sellers.domain listed in sellers.json and the ads.txt file, the updates develop a method to support identifying owned and operated domains and apps back to the entities that own the underlying domain or app.
2Scope
In Scope
Business relationships: This solution covers exclusive or primary monetization partnership relationships, where a global or regional entity becomes the most direct route to purchase inventory from a site or app. This solution also covers a way to identify owned and operated domains and apps back to the entities that own the underlying domain or app.
Reducing potential abuse vectors: These solutions are meant to help more closely tie validation between ads.txt and sellers.json.
a. Connecting the seller domain for PUBLISHER entries in sellers.json with the OWNERDOMAIN in ads.txt
b. Better representation of exclusive paths to inventory that contain more than one hop in the supply path.
Out of Scope
Business relationships: This solution does not cover a way to represent that you are the exclusive monetization partner of a particular ad format type. This was deemed too complex to represent in the ads.txt specification.
3Updates to Ads.txt & App-Ads.txt Standard
Please see the updates to the ads.txt standard here
The below example use cases seek to help answer, what is the relationship between the “seller” and the underlying domain being sold?
4Example Use Cases
Definitions:
- Manager - (see definition in spec for official definition) When the owner of the site does not manage monetization , the external, designated monetization partner is deemed the manager.. These partnerships can be global in scope, can be limited to a particular geography, or for new manager testing purposes, can be limited to a particular subdomain.
- *A note on the use of MANAGERDOMAIN vs INVENTORYPARTNERDOMAIN: MANAGERDOMAIN is used to represent a primary or exclusive programmatic seller of a publisher’s inventory and signify when a manager is the most Direct path to a publisher's inventory. Managers are additional participants in the end-to-end transaction between a publisher and a buyer. These relationships are generally governed on a revenue sharing agreement where the manager is paid a percentage of sale of inventory they sell on behalf of the publisher. It is expected that managers are also represented in the schain object of a bid request as the terminal node. In contrast, INVENTORYPARTNERDOMAIN is used to represent a company that owns or has the rights to sell a portion of ads on the underlying app where they are listed. This is expected to be used when the company has an “inventory sharing” agreement in place with the underlying CTV/OTT app. In these transactions it is expected that the inventory partner is the final payee in a transaction and receives all proceeds from the ads sold. Additionally, inventory partner domain is expected to be used primarily for CTV/OTT inventory, where “inventory sharing” is common.*
- Proprietary Placement Provider - Proprietary placements are ad units for which the publisher delegates monetization control to an intermediary. This intermediary might issue bid requests directly to DSPs, or it might issue bid requests via reselling exchanges.
- GEO - Geographical region, in the use cases below GEO is representative of a country. This is to support the MANAGERDOMAIN specification definition that allows for a manager per country declaration.
CASE A: Publisher inhouse monetization
Business scenario: The publisher monetizes their inventory internally. They operate the seats on the exchanges: Publisher.com is the business entity that owns site.com
Publisher -> Exchange -> DSP:

| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1234 is owner of site.com and DIRECT path of inventory |
CASE B: Publisher managed monetization
Business scenario: This case represents the publisher monetizing their inventory through an exclusive monetization partner. While the supply path includes multiple hops, it is still the most direct route from a Supply Path Optimization perspective to purchase the inventory.
Publisher -> Manager -> Exchange -> DSP:

See request/response table on the next page.
| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1235 is the monetization Mapager of site.com and is the most DIRECT path to inventory. Seller 5678 is the owner of site.com which has a DIRECT relationship with Manager |
CASE C: Publisher managed monetization; country specific
Business scenario: This case represents the publisher monetizing their inventory through an exclusive monetization partner in a specific country. While the supply path includes multiple hops, it is still the most direct route from a Supply Path Optimization perspective to purchase the inventory.
Publisher -> Manager + GEO -> Exchange -> DSP:

See request/response table on the next page.
| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1236 is the monetization manager of site.com for DE only and is the most DIRECT path to inventory. Seller 9786 is the owner of site.com which has a DIRECT relationship with Saleshouse DE |
CASE D: Publisher inhouse monetization for proprietary placement type
Business scenario: The publisher monetizes their inventory internally. They operate the seat with the proprietary placement type directly. Publisher -> Proprietary Placement -> DSP
See request/response table on the next page.:

| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 45678 is the owner of site.com and DIRECT path to proprietary placement inventory. |
CASE E: Resale of publisher inhouse monetization for proprietary placement type
Business scenario: The publisher monetizes their inventory internally. They operate the seat with the proprietary placement type directly. The proprietary placement vendor then sells the inventory on an exchange.
Publisher -> Proprietary Placement -> Exchange -> DSP:

See request/response table on the next page.
| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1238 is not the owner or manager of site.com and is a reseller path to underlying inventory. Seller 45678 is the owner of site.com and Proprietary Placement is a DIRECT path to the underlying inventory. |
CASE F: owned inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
Business scenario: The entity selling the inventory is both a media owner and a monetization manager for different pieces of inventory. The below illustrates what would be expected for a piece of inventory that is owned by the entity.
Publisher -> Exchange -> DSP:

See request/response table on the next page.
| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1240 is owner of site.com and DIRECT path to inventory |
CASE G: Resold inventory from Media Owner + Monetization Manager that has BOTH owned and resold inventory
Business scenario: The entity selling the inventory is both a media owner and a monetization manager for different pieces of inventory. The below illustrates what would be expected for a piece of inventory that is being sold by the entity on behalf of another publisher.
Publisher -> Manager -> Exchange -> DSP:

See request/response table on the next page.
| Bid Request | Publisher's Authorized Sellers (Ads.txt) | Sellers.json | Validation | Answer |
|---|---|---|---|---|
| | | | Seller 1240 is not the owner or manager of site.com and is a RESELLER path to underlying inventory. Seller 123xyz is the owner of site.com and ZYZ Media is a DIRECT path to the underlying inventory. |
5Implementation Guidelines
Publisher Guidance
- It is recommended that you publish OWNERDOMAIN= even if your website domain and owner domain are the same
- Specifically for sellers that are both owners and sellers it is highly recommended that they publish OWNERDOMAIN so that buyers can tell the difference between owned inventory and resold inventory. Another recommendation when possible is to separate their selling seats to more clearly represent each type of supply path.
- It is recommended that you only use MANAGERDOMAIN if a majority of your inventory is managed by a single entity. The exact interpretation of MANAGERDOMAIN is at the discretion of Ads.txt consumers (e.g. validators, measurement and anti-fraud solutions, buying platforms, etc), and may have SPO implications. For example, if the same inventory is available through multiple sellers, and you still use MANAGERDOMAIN, buyers will likely treat the other nonmanager accounts as RESELLER entries.
- Conflicting MANAGERDOMAIN entries (e.g., multiple MANAGERDOMAIN for the same country) should not be used and will likely be ignored by the consumers of the information.
- This work is being done in part to help clean up the accuracy of ads.txt files. Please take this opportunity to validate that all DIRECT entries in your file are references to seller accounts that you have direct account control of.
- All accounts authorized in your ads.txt that are PUBLISHER in the corresponding sellers.json file should also have a sellers.domain in sellers.json that matches the OWNERDOMAIN in your ads.txt.
SSP/Exchange Guidance
- These validations of OWNERDOMAIN and MANAGERDOMAIN require a check against ads.txt AND sellers.json.
- Ensure that the sellers.domain in sellers.json matches the OWNERDOMAIN and MANAGERDOMAIN for selling accounts respectively.
- Consider more strictly validating ads.txt entries to ensure that they contain the correct field 3 value. SSPs/exchanges know what relationship they have with their publishers, and therefore can easily check if their publishers are correctly declaring field 3 in their ads.txt files.
DSP Guidance
- These validations of OWNERDOMAIN and MANAGERDOMAIN require a check against ads.txt AND sellers.json. It is recommended that DSPs consume and action against this data for risk mitigation benefits and SPO.
- The exact interpretation of MANAGERDOMAIN is at the discretion of each DSP, and may have significant SPO implications. It is recommended that if the DSP differs from the below guidelines, publish clear guidelines to publishers, SSPs, and partners before enforcement of any policies regarding MANAGERDOMAIN.
- The recommendations for DSPS are:
- If you see a MANAGERDOMAIN declared, but still see significant inventory available through other sources, indicating that the MANAGERDOMAIN is not exclusive, you may treat the other traffic sources as RESELLERs of inventory, but be aware that there are non-abusive use cases that are not exclusive. Additional verification is recommended.
- If the same inventory is available both from OWNERDOMAIN sellers and MANAGERDOMAIN sellers, the MANAGERDOMAIN entry is likely mis-marked (since selling inventory directly and via a manager implies the publisher is not outsourcing their yield management to an external entity like a sales house).
- It is recommended that if there is more than one MANAGERDOMAIN for the same country that consumers treat it as if there is no MANAGERDOMAIN declared for that country (ie, that declaration is invalid).
- It is expected that ad opportunities monetized by the manager, the domain listed in MANAGERDOMAIN is also that of the node representing the originating publisher in a complete supply chain object.
Sources
InteractiveAdvertisingBureau/Supply-Chain-Validation ↗ · Explainer Guide.md
commit 7682963ae241 · fetched 2026-10-29 · ingested
Not stated in the document; the repository README's CC-BY 3.0 line names Ads.txt only
No diagrams anywhere; CASEs are expressed as bold-labelled fact lists
InteractiveAdvertisingBureau/Supply-Chain-Validation ↗ · Implementation Guidance.md
commit 7682963ae241 · fetched 2026-10-29 · ingested
Not stated in the document; the repository README's CC-BY 3.0 line names Ads.txt only
The seven CASE diagrams still link to seven different commits of the pre-rename repository; the official URLs are recorded as-is and not mirrored