Reporting and money

ads.txt and sellers.json

ads.txt and sellers.json tell buyers who may sell a site’s or an app’s inventory. Visor’s line is issued after the traffic check, and it is not listed here.

Last updated · 8 min read

On this page

ads.txt and sellers.json are public files buyers use to see who is allowed to sell a site’s or an app’s inventory. The specs come from IAB Tech Lab. Visor’s own line, Visor’s sellers.json file, and Visor’s SupplyChain node are not published yet.

What ads.txt is

ads.txt means Authorized Digital Sellers. It is a plain-text file a site owner posts at the root of the domain, at /ads.txt. Each record names an advertising system, the seller account in that system, and whether the relationship is DIRECT or RESELLER. Buyers can read the file and drop inventory that names a seller the site did not list.

IAB Tech Lab publishes the spec, including app-ads.txt, at iabtechlab.com/ads-txt. The file is only authoritative because the site owner is the one who can place it, in the same way robots.txt is. A file on someone else’s domain does not authorize your inventory.

The original spec asks for Content-Type: text/plain, served over HTTP or HTTPS, at the path /ads.txt on the root domain rather than on a subdomain. Later versions of the spec add optional variable lines, such as OWNERDOMAIN and MANAGERDOMAIN. Visor does not require those variables. Add a variable only when you mean it for your own file. Do not add one because a sample somewhere else had it.

app-ads.txt

app-ads.txt is the same idea for an app. The record format matches ads.txt. The file name is app-ads.txt, and it is posted on the developer website listed in the app store, at the root of that site. It is not a file inside the app binary, and it is not a screenshot in the store listing.

If the store listing names one website and you host the file on a different marketing domain, buyers that follow the spec will look at the website in the listing. Use the site you actually list. Visor does not publish a separate crawler rule.

The line format

A record is one line. Fields are separated by commas. The shape is <ad system domain>, <seller account ID>, <DIRECT|RESELLER>, <cert authority ID optional>.

The four fields
FieldWhat it is
Ad system domainThe domain of the advertising system that is authorized to sell.
Seller account IDThe publisher’s or seller’s account id inside that system.
DIRECT or RESELLERDIRECT: the site or app owner controls that account. RESELLER: another seller is authorized to resell, and that seller controls the account.
Certification authority IDOptional. In the spec, a certification authority id. Omit it unless the line you were issued includes it.

A line that starts with # is a comment. Blank lines are ignored by the spec. One record per line. Do not wrap a record across two lines. DIRECT and RESELLER are the relationship. They are not a quality score, and they are not something you pick because DIRECT sounds better.

The Visor line

Your exact Visor line, or lines, are issued after the traffic check passes. They are sent with your publisher agreement. They are not in the sample below. The sample uses placeholders so you can see the shape. AD_SYSTEM_DOMAIN is not our domain. YOUR_PUBLISHER_ID is not an account id. Omit the optional certification-authority field unless the line you were issued includes it.

Illustrative: authorized-seller recordtext
# Illustrative only. Not a Visor line. Do not publish this.
# AD_SYSTEM_DOMAIN and YOUR_PUBLISHER_ID are placeholders.
# A fourth field, a certification authority id, belongs only if the issued line includes it.
AD_SYSTEM_DOMAIN, YOUR_PUBLISHER_ID, DIRECT

Both tabs are the same placeholder record. The difference is the file name and the host, which the comments name. Neither tab is a line you should paste into production. When a real line is issued, copy that line. Do not edit the domain, the account id, or DIRECT versus RESELLER unless the issued line says to.

A publisher ID for the ad request is also issued after the traffic check, not before. Quickstart covers that ID. It is not automatically the seller account id in ads.txt. Use the ads.txt line you were issued, field for field. Sign-in is not connected yet, so the line is not waiting behind a login on this site.

Where to host the file

  1. Web: the root of the domain

    Serve plain text at https://<your-domain>/ads.txt. A path such as /ads/ads.txt is the wrong place. An HTML page with the same words is the wrong file.

  2. Use the domain you sell

    The spec tells publishers to post /ads.txt on the root domain, not on a subdomain. If both a www host and an apex host answer for you, know which one a buyer will fetch. Visor does not publish its own crawler rule.

  3. App: the developer website in the store

    Serve app-ads.txt at the root of the developer website listed in the store. Do not rely on a file that exists only inside the binary.

  4. Keep it public

    The file has to load without a login. A cookie wall or an interstitial in front of /ads.txt hides the records from buyers.

  5. Add only lines you were given

    Each record should be a system you authorized. A Visor record waits until Visor issues it, after the traffic check.

sellers.json

sellers.json is the file an advertising system publishes about its sellers. IAB Tech Lab describes it at iabtechlab.com/sellers-json. Buyers use it to see who a seller account id belongs to: a publisher, an intermediary, or both, and on which domain, unless the entry is marked confidential. The system posts the file. The publisher does not post Visor’s sellers.json on the app’s domain.

Posted together with ads.txt, the pair answers two questions. ads.txt says which systems the site authorized. sellers.json says which sellers those systems claim to work with. A buyer can then check that the seller id in a bid request is a seller the system has named.

The SupplyChain object

The OpenRTB SupplyChain object, often called schain, travels with a bid request. It lists the entities that handled that request, as a chain of nodes. Each node names an advertising system and a seller id on that system. Buyers use the chain, plus ads.txt and sellers.json, to see the path. The chain is a list of companies. It is not a person. It does not carry a name, an email, a phone number, or a cookie.

IAB Tech Lab documents the object beside sellers.json. Versions of the object have changed over time, including what counts as a node. This page does not pin Visor to a version. We have not published a Visor node.

Check the file

There is no Visor validator on this site. Check the file the way a buyer would: fetch it.

  1. Open https://<your-domain>/ads.txt in a browser. For an app, open https://<developer-website>/app-ads.txt.
  2. You should see plain text. If you see your homepage, a login, or a styled page, the file is missing, rewritten, or in the wrong place.
  3. Each live record has an ad system domain, a seller account id, and DIRECT or RESELLER. The fourth field is present only when it was part of the issued line.
  4. Comments start with #. A record does not.
  5. There is no Visor record unless Visor issued one. If you have not passed the traffic check, there should be no Visor line.
  6. The account id matches the line you were issued. It is not a neighbor’s id, and it is not the placeholder YOUR_PUBLISHER_ID.

Common mistakes

Common mistakes
MistakeWhat to do instead
Pasting a guessed Visor lineWait until Visor issues the line after the traffic check. Do not add one before that.
Using the placeholders from this pageAD_SYSTEM_DOMAIN and YOUR_PUBLISHER_ID are not real values.
Putting the file in a folderServe it at /ads.txt or /app-ads.txt on the root of the right host.
Serving HTMLServe plain text. A web page that contains the line is not the file.
Hiding the file behind a loginThe file has to load for a buyer who has no account on your site.
Hosting app-ads.txt only inside the appPost app-ads.txt on the developer website listed in the store.
Swapping DIRECT and RESELLERUse the relationship on the line you were issued.
Adding a certification authority idOmit the fourth field unless the issued line includes it.
Copying another app’s seller idUse the id on the line issued to you.
Publishing sellers.json for Visor on your domainsellers.json is published by the ad system. Visor has not published one.
Guessing a schain nodeLeave the node out of any doc you write until Visor publishes it.

Questions

Can I add a Visor line now?
No. Visor’s ads.txt line is not published yet. Do not add a Visor line until it is issued to you, after the traffic check.
Where does the file go for an app?
On the developer website listed in the store, as /app-ads.txt, in plain text. The record format matches ads.txt. The file does not live inside the app binary.
Does Visor publish sellers.json?
Not yet. Do not look for a URL, and do not write a sellers.json that claims to speak for Visor. This page will link the file once it is published.
What do I put in schain?
Nothing from this page. Visor’s SupplyChain node is not published. The OpenRTB field list is agreed at onboarding and stays on the locked OpenRTB page.

Was something unclear? Contact support