The Programmatic Supply Chain Playbook
The definitive guide to ads.txt, sellers.json, and protecting publisher monetization integrity in the programmatic ad tech ecosystem.
Chapter 1: The Foundation of ads.txt
In the programmatic advertising landscape, ads.txt (Authorized Digital Sellers) is the critical standard for domain authentication. Introduced by the IAB Tech Lab in 2017, this specification eliminated domain spoofing and established supply chain transparency.
Before ads.txt, advertisers lost millions to fraud as malicious actors tricked ad exchanges into misrepresenting low-quality inventory as premium domains.
How ads.txt Works:
Publishers host a publicly accessible ads.txt file at their root domain. This file acts as a cryptographic guest list, declaring exactly which IDs are authorized to sell their ad space.
A standard ads.txt entry looks like this:
google.com, pub-1234567890, DIRECT, f08c47fec0942fa0When a buyer (DSP) evaluates an ad request, they cross-reference the exchange ID against this file. If the entry is missing or incorrect, the request is flagged as unauthorized, preventing domain spoofing.
Chapter 2: The sellers.json Missing Link
While ads.txt identifies authorized sellers, sellers.json verifies the identity of the entities behind those account IDs. Launched in 2019, it provides the inverse validation required for a transparent supply path.
Sellers.json files are hosted by Supply-Side Platforms (SSPs) and ad exchanges. They list every seller on their platform, their legal name, and their relationship type.
The Programmatic Transparency Loop:
If ads.txt is the publisher saying "I authorize Account 123," then sellers.json is the exchange saying "Account 123 belongs to Publisher Y."
By cross-referencing these files, Demand-Side Platforms (DSPs) can perform Supply Path Optimization (SPO), ensuring an unbroken line of trust from advertiser to publisher. Any break in this loop leads to bid rejection.
Chapter 3: Decoding DIRECT vs. RESELLER
The relationship declaration (DIRECT vs. RESELLER) is the most critical field in an ads.txt entry. Mislabeling this field is a primary cause of silent revenue loss for publishers.
DIRECT Entries
Used when the publisher has a direct legal and financial relationship with the exchange. The publisher owns the seat and receives payments directly from the SSP.
RESELLER Entries
Used when a third-party monetization network (e.g., Mediavine, Raptive, Setupad) manages the inventory. These entries must match the "INTERMEDIARY" status in sellers.json.
The sellers.json Matching Rule:
An ads.txt DIRECT relationship must align with a PUBLISHER seller type in sellers.json. Similarly, RESELLER must align with INTERMEDIARY. Discrepancies here trigger SPO filters, causing buyers to drop bids.
Chapter 4: Why Mismatches Cost You Revenue
Modern Supply Path Optimization (SPO) algorithms used by major DSPs (like The Trade Desk and Google Display & Video 360) strictly enforce supply chain integrity.
Buyers demand the most direct, transparent route to inventory. If your supply path is malformed, you lose revenue silently.
Silent Revenue Leakage:
When a DSP detects a relationship mismatch or an unauthorized ID, they simply stop bidding on that path. They do not send notifications. This leads to unexplained drops in fill rates and CPMs that publishers often attribute to market fluctuations.
The AdOps Solution:
To maximize programmatic revenue, your ads.txt file must be a pristine, synced reflection of global exchange registries. Regularly removing closed lines, fixing syntax errors, and resolving relationship mismatches ensures buyers bid with absolute confidence.