{"id":5905,"date":"2017-09-28T17:03:00","date_gmt":"2017-09-28T15:03:00","guid":{"rendered":"https:\/\/yieldbird.com\/?p=5905\/"},"modified":"2024-07-22T19:27:15","modified_gmt":"2024-07-22T17:27:15","slug":"the-true-colors-of-ads-txt","status":"publish","type":"post","link":"https:\/\/yieldbird.com\/research-hub\/the-true-colors-of-ads-txt\/","title":{"rendered":"The True Colors of Ads.txt"},"content":{"rendered":"\n


The essential information about ads.txt<\/em>, its meaning, role and tips on how to implement this simple tool aiming to bring simplicity and clarity to the digital ad market in a few quick steps.<\/span><\/p>\n\n\n\n


What is all the fuss with ads.txt about?<\/h2>\n\n\n\n


Ads.txt<\/strong>, which stands for Authorized Digital Sellers<\/strong>, is a text file that is implemented in a publisher\u2019s web server to inform those on the buy-side about who is selling inventory programmatically. Originally, ads.txt was launched in May 2017 by the IAB to reduce domain spoofing and reselling in the open marketplace. <\/span><\/p>\n\n\n\n

What main purpose does it serve?<\/h3>\n\n\n\n


The IAB\u2019s ads.txt was supposed to bring simplicity and clarity to the digital ad market, while cutting down on fraud. But so far <\/span>only a fraction of the world’s top publishers<\/b><\/a><\/p>\n\n\n\n

The file itself is an IAB Tech Lab project developed to eliminate inventory fraud in the digital advertising industry. Just like how robots help search engines understand the contents of a website, the ads.txt helps buyers discover how a website\u2019s inventory is supposed to be sold<\/strong>. <\/span><\/p>\n\n\n\n

Simply put, the ads.txt<\/em> lists all the platforms that are authorized to sell the inventory, in terms of all the SSPs used and the specific accounts (seats) run by both the publisher (owned inventory) and resellers (represented inventory) respectively.<\/span><\/p>\n\n\n\n

\"how<\/figure>\n\n\n\n

How is ads.txt trending among the publishers?<\/h2>\n\n\n\n


The anti-ad-spoofing tool wasn\u2019t as well-received as initially expected. <\/span>An open letter to publishers about ads.txt<\/strong><\/a> recently released on Digiday says it all: \u2018Adopt or be blocked\u2019. <\/span><\/p>\n\n\n\n

Yet, publishers <\/span>aren’t rushing to adopt ads.txt<\/strong><\/a>, even though the tool was launched to \u201chelp ad buyers avoid illegitimate sellers that arbitrage inventory and spoof domains\u201d, and simultaneously help publishers sell their inventory more effectively.<\/span><\/p>\n\n\n\n

Grasping it all with clarity does take some time. Many publishers don\u2019t seem to understand how they can benefit from ads.txt<\/strong>. But apart from a clear case of a lacking awareness, there\u2019s also a much darker side to it. Some publishers aren\u2019t that willing to notify ad buyers that they rely on unauthorized resellers to drive demand for their inventory.<\/span><\/p>\n\n\n\n

It\u2019s no wonder that, according to MarTech Today<\/b><\/a>, only 34 out of the 500 most-trafficked sites in the U.S. use ads.txt so far.<\/span><\/p>\n\n\n\n

Why should you implement it?<\/h3>\n\n\n\n


Unfortunately, publishers see no direct benefit of the ads.txt implementation<\/strong>. At least for now. Some buyers are already using the file in search of reliable and high-quality inventory. Our experts at Yieldbird expect buyers to eventually stop spending on sites that don\u2019t have the ads.txt file implemented. <\/span><\/p>\n\n\n\n

Just like how they moved away from spending on sites that don\u2019t provide full URL transparency. <\/span><\/p>\n\n\n\n

How will the ad tech ecosystem respond to ads.txt?<\/h2>\n\n\n\n


It\u2019s difficult to say at this point. Whether or not publishers adopt ads.txt or take the risk of being blocked, experts expect that this initiative will gain momentum in the near future.<\/span><\/p>\n\n\n\n

\"whats<\/figure><\/h4>\n\n\n\n

Most of the leading SSPs are already advising publishers to use the ads.txt file<\/em>. The major DSPs are also expected to use this information and maybe even block domains that don\u2019t have the file yet. <\/span><\/p>\n\n\n\n

But even if that’s not going to be the case, some of the bigger buyer networks may implement their own crawlers to go through the domains and build their own custom whitelists. <\/span><\/p>\n\n\n\n

So far, the ads.txt has been implemented by several publishers<\/strong>, such as The Guardian or Agora S.A. But the statistics show that no more than 12.8% of publishers have an ads.txt file implemented so far, <\/span>according to the Ad Ops Insider<\/b><\/a>. Some of the big players are joining the game with some stats and clarifications to ease the new-standard-adoption pain. <\/span><\/span><\/p>\n\n\n\n

How to implement ads.txt in a few quick steps?<\/h2>\n\n\n\n


Just get in touch with the SSPs you\u2019re using to see what should be put in the ads.txt file<\/strong>. It\u2019s possible that you already received the e-mail containing this information in the past few weeks.<\/span><\/p>\n\n\n\n

On top of that, some of the SSPs have already published their own guidelines. Here\u2019s one <\/span>provided by Google<\/b><\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

The essential information about ads.txt, its meaning, role and tips on how to implement this simple tool aiming to bring simplicity and clarity to the digital ad market in a few quick steps. What is all the fuss with ads.txt about? Ads.txt, which stands for Authorized Digital Sellers, is a text file that is implemented […]<\/p>\n","protected":false},"author":17,"featured_media":20612,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"content-category":[],"class_list":["post-5905","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/posts\/5905","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/comments?post=5905"}],"version-history":[{"count":1,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/posts\/5905\/revisions"}],"predecessor-version":[{"id":33511,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/posts\/5905\/revisions\/33511"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/media\/20612"}],"wp:attachment":[{"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/media?parent=5905"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/categories?post=5905"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/tags?post=5905"},{"taxonomy":"content-category","embeddable":true,"href":"https:\/\/yieldbird.com\/research-hub\/wp-json\/wp\/v2\/content-category?post=5905"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}