Buyers increasingly ask one question before they bid: who is actually selling this impression, and through how many hands? If you run an exchange, you are one of those hands. Three public, simple standards answer the question: ads.txt (with app-ads.txt), sellers.json and the SupplyChain object. Get them right and buyers can trust your supply. Get them wrong and good demand quietly stops bidding.
ads.txt: who may sell a publisher's inventory
ads.txt is a text file that a publisher places at the root of its domain, for example example.com/ads.txt. Each line authorises one account:
exchange.example, 12345, DIRECT, abc123def456
exchange.example, 67890, RESELLER
- the domain of the advertising system, such as your exchange;
- the publisher's account ID in that system;
- the relationship: DIRECT if the publisher controls the account, RESELLER if someone else sells through it on the publisher's behalf;
- optionally, the certification authority ID of the advertising system, typically its TAG identifier.
Variables add context. CONTACT and SUBDOMAIN have been there from the start; version 1.1 added OWNERDOMAIN, the business domain of the inventory owner, and MANAGERDOMAIN, the company managing it on the owner's behalf.
app-ads.txt is the same idea for apps. The developer publishes the file on the website listed in the app's store page, and buyers find it through the store listing.
For an operator: every publisher whose inventory reaches you, directly or through a supply partner, needs a correct line for your exchange. Give your partners the exact lines, explain DIRECT versus RESELLER, and check that the lines are actually live.
sellers.json: who is behind each account
ads.txt names accounts; sellers.json names the businesses behind them. Each advertising system publishes one file at the root of its own domain, at /sellers.json:
{
"seller_id": "12345",
"seller_type": "PUBLISHER",
"name": "Example Media",
"domain": "example.com"
}
seller_idis the account ID that appears in publishers' ads.txt lines;seller_typeis PUBLISHER, INTERMEDIARY or BOTH;nameanddomainidentify the business. A seller can be marked confidential withis_confidential, which leaves those out, but the entry should still be there.
For an operator: your exchange is an advertising system, so you publish your own sellers.json on your own domain. On a white-label platform that is your brand's domain. Keep it in sync with your partner list: every seller ID that can appear in a request should be in the file, with the right type.
The SupplyChain object: the path of one impression
ads.txt and sellers.json are static. The SupplyChain object, usually called schain, travels inside each bid request and lists every company that handled that impression. In OpenRTB 2.6 it sits in source.schain; older integrations use source.ext.schain.
ver: the version of the object;complete: 1 if the chain reaches all the way back to the inventory owner, 0 if not;nodes: the hops in order. Each node hasasi, the domain of the advertising system (the same domain used in ads.txt and sellers.json), andsid, the seller's ID in that system, plus optional fields such ashp, which says whether the node takes part in the flow of payment.
For an operator: when you receive a request with an schain, pass it on and append your own node with your domain and the seller ID you assigned. Never drop or rewrite earlier nodes. A buyer who sees an incomplete or broken chain will usually bid less, or not at all.
How buyers check you
- They read the schain from the request.
- For each node they open
asi/sellers.json and look upsid. - They check the first node against the publisher's ads.txt or app-ads.txt.
- They count the hops and prefer the shortest fully declared path.
That is supply path optimisation in practice. Your exchange wants to be the short, clean, fully declared path, not an extra hop with missing entries.
Common operator mistakes
- Publishing sellers.json once and never updating it.
- Marking intermediaries as PUBLISHER.
- Passing requests on without adding your schain node.
- Accepting supply from publishers whose ads.txt does not list you.
None of these is hard to fix. The files are public, the formats are simple, and buyers check them automatically. Make them part of partner onboarding, not an afterthought.
Want to talk about your own setup? Get in touch with the Xendiz team.