• by Kenneth Suh , Op-Ed Contributor, November 2, 2017

Catfishing doesn’t just exist in the world of online dating. Ad buyers have been caught, too, purchasing inventory for what they think are premium sites, when in reality the ad placement shows up on a different site. This is known as domain spoofing and is a growing problem — which publishers like the Financial Times have helped to raise awareness of, by releasing reports about domain spoofing on its own site.

With an eye toward transparency, the Interactive Advertising Bureau introduced Ads.txt as a way to fight this type of fraud  — and it’s quickly gaining traction. Programmatic buyers are asking publishers to adopt Ads.txt as a way of making sure the inventory they are buying is actually from their sites.

In fact, Google’s DoubleClick Bid Manager recently stated that if you’re a supply-side platform that isn’t listed on a publisher's Ads.txt file in bid requests, then DBM will not bid.

Of course, this could be seriously painful for publishers, who potentially face lost revenue as a result of not implementing these text files. But given the speed of adoption, it can be difficult to keep up.

So here’s a breakdown of the issues surrounding Ads.txt and what publishers need to do to adopt it.

What is it?

Ads.txt stands for authorized digital sellers. It allows publishers to add a text file to their servers, which is then integrated into programmatic platforms. Security from a simple text file — who knew?

This method helps publishers clearly communicate who is authorized to sell their inventory, adding additional layers of transparency for programmatic buyers. It has been introduced into the OpenRTB spec to enable demand-side platforms to check whether or not the supply source they’re directly integrated into is authorized to sell inventory on behalf of the publisher that the supply has originated from.

Because the text file can only be posted by a publisher’s webmaster, partners within the ecosystem can be sure of the validity of inventory prior to purchase.

How does it work?

There are often two kinds of programmatic demand integrations — direct integration with DSPs, or through third-party exchanges. Either will work, but a direct integration provides publishers with not only added transparency, but also with the peace of mind to know their programmatic pipes are as streamlined as possible.

Ads.txt creates a public record, making it possible for programmatic buyers to purchase inventory only from these pre-authorized sellers. DSPs can then deploy web crawlers to collect all the Ads.txt files available.

Here’s g the IAB’s description of the process, “Example.com publishes Ads.txt on their web server listing three exchanges as authorized to sell their inventory, including Example.com’s seller account IDs within each of those exchanges.”

Why should I care?

The first reason is simple: to make more money. Fraudsters are out there eating up demand by pretending to be your brand and website. This provides everyone involved the confidence to know they're actually buying what they’re bidding for.

Additionally, with players like Google already jumping onboard to enforce adoption, it’s likely that more will follow. Being left out of some of the biggest demand platforms could lead to irreversible damage to any publishers, large or small, and their programmatic revenue stream.  

Getting started is simple. Reach out to receive information specific to your website from your supply partners and paste it into your Ads.txt file. It’s a simple way to fight a serious problem plaguing the industry.