I’ve spent the last couple of years being very on Twitter. Along with spending too much time scrolling/reading, I write there frequently and at length. It’s where I publish most of my adtech/disinformation research, and where I talk about my software projects.
Like a lot of Twitter users recently, I’ve been trying to work out if Mastodon is an alternative if/when it’s no longer viable to stay on Twitter. I have my doubts.
IAB Tech Lab recently released a new version of the ads.txt standard for comment. This 1.1 update defines two new variables — OWNERDOMAIN and MANAGERDOMAIN — that attempt to solve some outstanding issues with how seller relationships are expressed.
While these new variables provide useful extra data points, I’m concerned they won’t achieve the wide adoption necessary to make a meaningful difference, and that some of the changes are moving the standard in the wrong direction.
Domain spoofing — where ad inventory is misrepresented as being from a different site — is often talked about as a solved problem by adtech insiders. Despite this, USA Today and hundreds of local newspapers owned by Gannett were sending spoofed bid requests to multiple ad exchanges for over 9 months.
In the previous post I covered the ads.txt standard, and proposed a change to the definition of DIRECT to enable the industry to clean up mislabelled accounts and help tackle domain spoofing.
But it’s been over 4 years since ads.txt was released, and in the meantime it’s been joined by a pair of newer standards — sellers.json and SupplyChain object. Let’s take a look at these standards, and how they fit in with the proposed ads.txt update.
Programmatic advertising is a massive, complicated, and largely opaque industry. Thousands of companies buy and sell ad space across the web in real-time auctions, determining what ads you see and how much publishers get paid.
The ads.txt and sellers.json standards from the IAB Tech Lab have been touted as tools to provide much needed transparency, but problems with the interpretation, implementation, and enforcement of the standards have blunted their impact.
This is the first in a series of posts diving into these standards and their problems, and suggesting some potential solutions (or at least improvements).