ads.txt for Oath DSPs

Identify Oath on publisher’s ads.txt files.

Oath supports the industry-wide ads.txt initiative. We are partnering with both DSP's and supply sources to facilitate the enforcement of ads.txt files by our DSP partners.

What is ads.txt?

Ads.txt was created by the IAB to allow publishers to publicly declare the specific exchanges they work within the digital advertising space. The goal of ads.txt is to improve transparency and decrease fraud revenue.

How is the ads.txt file formatted?

The format for ads.txt file is: #< SSP/Exchange Domain >, < SellerAccountID >, < PaymentsType >, < TAGID >

This is an Oath example

#ads.txt file sample
 , 12000, DIRECT #banner, US, 3679, DIRECT #video, US, 20459933223, DIRECT # banner, US, 25980889636, DIRECT # banner, CA, 4577, DIRECT #banner, app

What instructions does Oath provide to publishers?

Step by step instructions for publishers can be found in the publisher's documentation section of our customer center.

What domains can I expect to see from Oath?

Depending on the Oath Ad Platform used one of the following domains will come from us.

Platform Domain
Video SSP
ONE by AOL: Display
DSP, Gemini

*Note the ads.txt file information applies to all Oath Ad Platforms.


Ads.txt FAQ’s

Q: Can I see a current example of a live ads.txt file?

A: View examples of live ads.txt files at or

Q: What is the Certification Authority ID? And does Oath have one?

A: A Certification Authority ID uniquely identifies the advertising system (this ID maps to the entity listed in Field #1). The Certification Authority ID is optional and appears in Field #4.

Oath is certified for malware (as of September 2018) by the Trustworthy Accountability Group (aka TAG). Our TAG ID is e1a5b5b6e3255540. Use our TAG ID on your ads.txt file for our entries.

More info and examples can be found in the IAB OpenRTB ads.txt Spec on pages 6 & 8.

Q: Are ID’s consistent across Oath Ad Platforms?

A: No, ID’s can vary from platform to platform as well as country to country. The Exchange/Seat ID would be the Publisher's Network ID. If the Pub is set up in both US and EU, they must enter two lines in their ads.txt file - one for each Network ID.

Q: Can I see a sample crawler for DSPs?

A: Yes, please reference the IAB page here.

Q: Do you have a sample bid request for Oath Ad Platforms SSP?

A: Yes, see the SSP sample bid request below for mobile.

"publisher": {
       "id" : "17382",
       "Name" : "EA Mobile",
       "Ext" : {
       "Nex_else" : 0

Q. Do you have a sample bid request for ONE by AOL: Display where we can see publisher ID?

A: Yes, see the ONE by AOL: Display sample bid request below.

"site": {
     "id": "50-1234",
     "page": "",
     "publisher": {
     "id": "50"

Q: Is Oath actively crawling the web for ads.txt files?

A: Yes, we started crawling in September 2017.

Q: What happens if no ads.txt file is present?

A: DSPs can interpret the absence of ads.txt files in two ways:

  • Assume that no advertising is unauthorized because no file is present
  • Reach out to the publisher to get authorization to sell inventory

Q: What if DSPs want to target/exclude based on one or more of these options?

  • Authorized reseller
  • Non-Participating
  • Non-authorized reseller

A: Targeting (including or excluding seller’s inventory) is entirely controlled by the DSP. Once ads.txt becomes widely adopted, we anticipate DSP’s will make bid decisions based on information they find in specific ads.txt files.

Still have questions? Please reach out to your Oath Demand Services manager.

Have more questions? Submit a request