ads.txt for Oath DSP's

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 with in 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 fles is: #< SSP/Exchange Domain >, < SellerAccountID >, < PaymentsType >, < TAGID >

This is an Oath example (note: it does not include the optional TAGID)

adstxt_fileSample.png

 

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 platform used one of the following domains in the table below may come from Oath. 

Platform Domain
ONE by AOL: Mobile aol.com
ONE by AOL: Video advertising.com
ONE by AOL: Display adtech.com, aolcloud.net
Brightroll from Yahoo! btrll.com

*Please note the ads.txt file information applies to all ONE for AOL platforms, not just ONE for AOL: Mobile.

 

Ads.txt FAQ’s

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

A: View a Live example ads.txt file.

Q: What is the Certification Authority ID? And does ONE by AOL have one?

A: A certification Authority ID uniquely identifies the advertising system (this ID maps to the entity listed in field #1). One certification authority is the Trustworthy Accountability Group (aka TAG). The TAGID is optional and would appear in field #4. More info and examples can be found in the IAB OpenRTB ads.txt Spec on pages 6 & 8.

NOTE: Oath is currently in the process of obtaining the TAG certification, but we are not yet certified. This field is optional and not required in the ads.txt file.

Q: Are ID’s consistent across AOL’s platform?

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 in Marketplace (for ONE by AOL: Display). 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 buyers?

A: Yes, please reference the IAB page here.

Q: Do you have a sample bid request for ONE by AOL: Mobile?

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

"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": "http://www.aol.com",
     "publisher": {
     "id": "50"
     }
 },

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

A: No, not yet, but we will be in Q3 of 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 authorized because no file is present
  • Reach out to the publisher to get authorization to sell inventory

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

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

A: Currently, DSP’s read the publisher's ads.txt files and only resell what is on that file. If a DSP wants to more selectively target/exclude inventory, they must do that on their end until the DSP version of ads.txt is complete.

Still have questions? Please reach out to your ONE by AOL Demand Services manager.

Have more questions? Submit a request