No. The official IAB Tech Lab material cited here does not say that exclusive: true in adagents.json removes, supersedes, or invalidates an authorization listed as RESELLER in a publisher’s separate ads.txt file. The records serve different purposes: use ads.txt to check authorization, sellers.json to identify sellers and intermediaries, and the OpenRTB SupplyChain object to inspect the parties in a bid-request path.
What the exclusivity flag does—and does not establish
An exclusivity value in one file is not, on the evidence available in the official sources cited below, an automatic edit to another file. In particular, it does not by itself retire an ads.txt RESELLER line. Treat the flag and the seller record as declarations that need to be checked in their own context, rather than assuming one silently overrides the other.
As an Amazon Associate I earn from qualifying purchases.
This is a standards-based reading of the cited IAB Tech Lab material, not a legal ruling or an exhaustive review of every possible adagents.json implementation. IAB Tech Lab describes the supply-chain records as complementary, and cautions against terminology that duplicates concepts already represented elsewhere. IAB Tech Lab’s discussion of reading ads.txt addresses the distinction.
What each record is for
| Record | Question it answers | What to inspect |
|---|---|---|
ads.txt |
Which advertising systems has the publisher authorized to sell its inventory? | The system, seller ID, and relationship value, such as DIRECT or RESELLER. |
sellers.json |
Who is the seller or intermediary represented by a seller ID? | The seller identity and relationship published by the advertising system. |
| OpenRTB SupplyChain object | Which parties handled the bid request along its path? | The nodes representing the parties that sold or resold the request, and whether the path is complete. |
These distinctions are reflected in IAB Tech Lab’s explanation of ads.txt, sellers.json, and SupplyChain and its CTV Programmatic Guide. A line in ads.txt addresses authorization; it is not a substitute for identifying the entity or tracing the transaction.
#1 Best Overall
- 【Built-in Lifetime Free CMS & Remote Management】Control your digital signage display anytime through the free lifetime Cloud CMS using your PC, tablet, or smartphone. Upload content remotely, create playlists, schedule playback, manage multiple displays, split screens, and update promotions in real time. USB plug-and-play is also supported for quick local content changes.
- 【700 Nits Commercial Display for 24/7 Business Use】Designed for continuous commercial operation, this 18.5-inch desktop digital menu board delivers 700 nits of brightness for clear visibility in cafés, restaurants, reception areas, and retail stores. Powered by Android 12 with 2GB RAM and 32GB storage, it ensures stable, reliable playback every day.
- 【Designed for Countertops, Checkout Areas & Reception Desks】Includes a sturdy desktop stand with landscape and portrait display options to fit different business layouts. Perfect as a digital countertop display for coffee shops, bakeries, salons, hotel receptions, trade shows, retail counters, waiting rooms, and customer service desks.
- 【HD Display with Flexible Connectivity】Enjoy sharp 720P HD visuals with a wide viewing angle for menus, promotions, and advertisements. Supports HDMI, LAN, TF card, USB 2.0, USB 3.0, and DC connections, giving businesses flexible options for local or cloud-based content management.
- 【Built to Increase Customer Engagement】Transform your business with dynamic menus, promotional videos, product showcases, welcome messages, and advertising displays that capture customer attention better than printed signs. Ideal for restaurants, cafés, bakeries, retail stores, hotels, clinics, exhibitions, and other commercial environments.
How MANAGERDOMAIN relates to DIRECT and RESELLER
Seller lines describe authorization relationships
DIRECT and RESELLER are values on ads.txt seller records. They describe the publisher’s authorization relationship with the named advertising system and seller account. Their presence should be evaluated as an authorization declaration, not treated as a synonym for an exclusivity flag in a different file.
MANAGERDOMAIN identifies a monetization manager
In ads.txt 1.1, the optional MANAGERDOMAIN variable identifies the business domain of a publisher’s primary or exclusive monetization partner. It is intended for circumstances where the owner does not manage monetization globally or in a particular country; the listed manager is not the publisher. A value can apply globally or to a country, with one manager per country. The ads.txt 1.1 specification explains the variable and its intended use.
Rank #2
That manager declaration is distinct from the authorization relationship on a seller line. IAB Tech Lab’s ads.txt 1.1 Implementation Guide recommends validating OWNERDOMAIN and MANAGERDOMAIN against both ads.txt and sellers.json. If a manager is declared but significant inventory remains available through other sources, the guide says buyers may treat those sources as resellers while accounting for legitimate non-exclusive arrangements and seeking further verification. It also flags a manager declaration alongside direct OWNERDOMAIN sellers as a possible mis-marking that warrants attention.
The guide leaves the precise interpretation of MANAGERDOMAIN to DSP discretion and recommends that DSPs publish clear policies before enforcing it. This is implementation guidance, not a universal instruction to delete a seller line whenever another file includes an exclusivity field.
How to audit a disputed RESELLER line
- Read the publisher’s current ads.txt. Record the exact seller line, including the advertising-system domain, seller ID, and whether it is marked
DIRECTorRESELLER. - Check the advertising system’s sellers.json. Use it to verify the identity and seller relationship associated with that ID.
- Compare owner and manager declarations. Check
OWNERDOMAINandMANAGERDOMAIN, including any country-specific value, against the actual commercial arrangement and the relevantads.txtandsellers.jsonrecords. - Inspect the bid-request path. Review the OpenRTB SupplyChain object for the nodes involved and whether the path is complete.
- Investigate discrepancies under a documented policy. Apply the DSP’s published validation rules and seek additional verification where needed. Do not infer that
exclusive: trueautomatically removes anads.txtline.
IAB Tech Lab also describes Supply Chain Validation datasets and APIs for checking ads.txt and app-ads.txt entries against sellers.json. Such checks can support an audit, but the declarations still need to be interpreted according to their distinct roles.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to conclude when the records disagree
A mismatch is a reason to investigate the publisher’s authorization, the identity behind the seller ID, the manager relationship, and the transaction path. It is not, on the cited evidence, proof that an adagents.json exclusivity flag has changed the contents or validity of ads.txt. Keep the checks separate and make any enforcement decision under a clear, documented DSP policy.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
