Ads.txt is IAB (Interactive Advertising Bureau)’s newest fraud-fighting initiative. It stands for “Authorized Digital Sellers,” and the aim of the initiative is to increase transparency in the way that programmatic advertising is sold to protect buyers from spoofers. Programmatic advertising, if you’re not in the industry, is media buying in which bots programmed to buy certain audiences buy from other bots programmed to offer inventory to those audiences. Untouched by human hands, programmatic advertising is often touched by fraudsters and malware purveyors.
In 2017 the digital media industry decided it was time to take action, before the entire universe of ad supported content vanished in a wave of ad blockers. Among the many other initiatives is Ads.txt:
(which )works by giving verified publishers and distributors an easy way to declare, publicly, the companies that they allow to sell their digital inventory. They do this by preparing and publishing the “/ads.txt” file, creating a public record of Authorized Digital Sellers and helping buyers to quickly identify which sellers are allowed to handle ad inventory for which publishers.
This makes it much harder for scammers to profit from selling fake inventory and gives buyers peace of mind that the ad space they buy is authentic.
By the time you read this post, over 100,000 ads.txt files will have been published. 750 of the comScore 2,000 will have ads.txt files and over 50% of inventory seen by DoubleClick Bid Manager will have come from domains with ads.txt files. Beginning in November, DoubleClick Bid Manager and AdWords stopped buying ads from ad networks / exchanges not declared on Ads.txt.
Google also says that “DoubleClick Ad Exchange and AdSense publishers that use ads.txt are protected against unauthorized inventory being sold in Google auctions.” To do this, Google “crawls daily over 30m domains for ads.txt files.”
The rapid adoption of Ads.txt shows how much of the market is controlled by Google. But this doesn’t make the initiative less valuable. Domain spoofing has been a huge problem on both the supply and demand sides, and we are happy to see this initiative and help our publishers adopt it.
If you’re a publisher, you need to implement the ads.txt text file on your root domain, listing the exchanges that are authorized to sell your inventory and including your seller account ID for each exchange.
Your seller account ID, sometimes called your publisher ID or seller network ID, is the ID that’s linked to your account on an exchange or supply-side platform (SSP). This is important because this part can’t be “spoofed.”
When you take part in programmatic real-time bidding, this ID should be transmitted through the OpenRTB protocol as the publisher ID, along with the Publisher.Domain in the Publisher object. If you’re using a different RTB protocol, it might be called “seller_network_id,” member or seat ID.
Ads.txt is also important for buyers, who are the ones paying the bills and the ones demanding more transparency. They have been almost literally throwing out money on online exchanges, and finding their brands in places that are destructive or irrelevant. No wonder they’re finally done with all this, and have demanded changes. Especially this year the ANA and the MRC have become loud players in demanding reform, and Mark Prichard of Procter and Gamble, the country’s largest advertisers, has been on a one-man tirade.
As a private platform, ZEDO is individually secure, and as an ad server we have our protections in place.
We are getting there, folks. Digital advertising is too large an industry to be so rife with corruption. We need to clean up, and we will. Ads.txt is only one initiative.