The total number of Alexa Top 5000 publishers using the IAB’s ads.txt technology is 1,088, or 21.76%. That’s according to research from Pixalate and is reflective of the marketplace as of February 19, 2018.
About 21.76% of Alexa Top 5000 sites — and 49.48% of Pixalate Top 5000 sites — are using ads.txt
The number of premium domains (Top 5000 Alexa domains) using ads.txt is 1,088, or 21.76%.
It’s important to note that not all Alexa 5000 domains support programmatic. When looking at only the top 5000 programmatically-supported URLs in terms of ads.txt adoption, Pixalate sees a total of 2,474 sites supporting ads.txt (49.48%).
According to data from Pixalate, collected between August and February 2018, using a sample of over 7 million unique URLs, about 1.81% of all publishers are using ads.txt. You can download the full list of sites using ads.txt.
|Total domains crawled||7,530,571|
|Domains with Ads.txt (as of 1-16-18)||136,001|
What is the IAB’s ads.txt initiative?
According to the IAB: “The mission of the ads.txt project is simple: Increase transparency in the programmatic advertising ecosystem. Ads.txt stands for Authorized Digital Sellers and is a simple, flexible and secure method that publishers and distributors can use to publicly declare the companies they authorize to sell their digital inventory.”
One of the goals is to prevent fraudsters from spoofing domains. If there is a public ledger of authorized sellers, then masking becomes more difficult for fraudsters. The goal is for widespread adoption, which would make most of the programmatic ecosystem “safer” in terms of knowing who the buyers and sellers in a particular transaction are.
What are some publishers that are using ads.txt?
Below is a list of 25 sites using ads.txt, according to Pixalate’s research. (To download the full list of sites using ads.txt, go here.)
Which publishers are not using ads.txt (as of 10-10-17)?
Below is a list of large publishers not using ads.txt as of September 18, 2017.
- msn.com (ads.txt added as of January 2018)
- aol.com (ads.txt added as of 10-10-17)
- zillow.com (ads.txt added as of 12-18-17)
- nfl.com (ads.txt added as of 10-17-17)
- cnn.com (ads.txt added as of 10-16-17)
- mlb.com (ads.txt added as of 11-27-17)
- ibtimes.com (ads.txt added as of 10-20-17)
- usatoday.com (ads.txt added as of 10-16-17)
- mashable.com (ads.txt added as of 11-13-17)
- realsimple.com (ads.txt added as of January 2018)
- thehill.com (ads.txt added as of 12-18-17)
- mapquest.com (ads.txt added as of February 2018)
- cbssports.com (ads.txt added as of 10-10-17)
- reuters.com (ads.txt added as of 10-16-17)
- today.com (ads.txt added as of 10-10-17)
- huffingtonpost.com (ads.txt added as of 10-10-17)
- newsweek.com (ads.txt added as of 10-20-17)
- people.com (ads.txt added as of 11-6-17)
- cbs.com (ads.txt added as of 10-16-17)
- definition.org (ads.txt added as of 11-13-17)
Which ad exchanges are plugged into the most ads.txt inventory?
- Top five ad exchanges based on the amount of root domains they are present on:
- Rubicon Project
- Index Exchange
- Top 5 exchanges that have a direct seller relationship, based on number of records:
- Rubicon Project
- Index Exchange
- Top 5 exchanges that have a reseller relationship, based on number of records:
How can I find out if a site is using ads.txt?
It’s easy to find yourself. Type in a website, and simply ad /ads.txt at the end of the URL. For example, espn.com/ads.txt brings you to a page that looks like this:
Each line is called a "record." Within each record, you see which sellers have been verified by the publisher.
In the ESPN example, we see that Google is verified as both a direct and reseller partner (with multiple unique IDs associated with its reselling), Teads is a verified direct partner with two unique IDs, and Rubicon Project is a verified reseller with one unique ID.
The second column in each record is the publisher ID.
Here’s the explanation from Google:
“The identifier associated with the seller or reseller account within the advertising system in field #1. This must contain the same value used in transactions (i.e. OpenRTB bid requests) in the field specified by the SSP/exchange. Typically, in OpenRTB, this is publisher.id. For OpenDirect it is typically the publisher’s organization ID.”
Basically, the second column means that the publisher ID on Google AdX is authorized to sell espn.com. However, espn.com only directly controls the publisher ID that has the word “DIRECT” in the third column.
The total number of unique records is much lower than the total number of records
In the above image showing ESPN’s ads.txt file, each line is called a “record.”
Google led the way with 761 unique records. AppNexus (312) and OpenX (279) were second and third, respectively, while Index Exchange (228) and Rubicon Project (201) rounded out the top five. Most other exchanges had fewer than 100 unique records.
However, the total number of records is much higher than this — and it might lead to some confusion. For example, despite having 761 unique records, Google AdExchange sees 51,879 total records.
Repetition is caused by subdomains, which were initially not supported by the initiative, but are now supported as of the September 1, 2017, update (Version 1.0.1).
What does this all mean?
While the initiative launched just a few months ago (announced in May 2017), uptake has still been slow. With fewer than 5%-10% of top sites adopting the program — depending on which metrics you use to determine "top sites" — it's clear that the industry in general has not been quick to implement ads.txt despite widespread discussions about transparency and quality.
However, only recently have buyers put pressure on sellers to effectively "adopt ads.txt or be blocked," as Liane Nadeau, VP, Director of Programmatic at DigitasLBi, put it in a guest post on Digiday. There could be amplified pressure to adopt ads.txt throughout Q4 2017.
Pixalate intends to keep tabs on the growth of ads.txt adoption both across the top domains, and across the entire web.
Download the full list of sites that have ads.txt implemented today.
Want more data-driven insights? Sign up for our blog!