The Transparency Blueprint: Understanding the Role and Evolution of Sellers.json in Programmatic Advertising

In the labyrinthine world of programmatic advertising, where billions of impressions are traded in milliseconds, the challenge of verification has long been a primary concern for marketers. While the industry has made significant strides in fraud prevention, one specific tool—sellers.json—has emerged as the definitive, albeit imperfect, bedrock of supply-path transparency. Created by the Interactive Advertising Bureau (IAB) Tech Lab in 2019, this public-facing JSON file serves as the vital link between anonymous numeric seller IDs and the legal entities behind them.

The Core Mechanism: How Sellers.json Functions

At its most fundamental level, sellers.json is a standardized directory hosted at the root domain of every major advertising system, such as a Supply-Side Platform (SSP) or an ad exchange. Its primary purpose is to provide a mapping mechanism. In the digital advertising ecosystem, a bid request is essentially a data packet containing a seller ID—a mere string of characters. Without a reference point, a buyer (such as a Demand-Side Platform, or DSP) has no way of verifying whether that ID belongs to a legitimate publisher, a reputable reseller, or a malicious fraud operation.

The specification requires that advertising systems named in a publisher’s ads.txt file, or referenced within a SupplyChain object, host this file at a fixed location: /sellers.json. The file must be served as a JSON object, containing a version (currently stuck at "1.0") and a sellers array. Each entry includes the seller_id, the seller_type (PUBLISHER, INTERMEDIARY, or BOTH), and, unless marked as "confidential," the entity’s name and domain.

The rule that provides the file with its teeth is a simple but critical mandate: "It is invalid for a seller_id to represent multiple entities." This prevents the common obfuscation tactic where one ID acts as a catch-all for various businesses, ensuring that the supply chain remains traceable back to a single source.

Chronology: A Seven-Year Journey of Transparency

The trajectory of sellers.json has been marked by initial resistance, a slow climb toward industry-wide adoption, and ongoing pressure for refinement.

• 2017: The Precursor. The IAB Tech Lab releases ads.txt, allowing publishers to authorize which exchanges can sell their inventory. While effective at curbing domain spoofing, it left a "transparency gap"—buyers knew which exchange was selling, but they didn’t know who was behind the account ID.
• April 2019: The IAB releases the draft of sellers.json and the SupplyChain object for a 30-day public comment period, aiming to provide a granular look into the full programmatic chain.
• July 2019: Both specifications are officially finalized.
• August 2019: Index Exchange becomes one of the early movers, adopting the standard immediately.
• June 2020: Google Ad Manager begins supporting the standard, though the initial data quality is poor. Jounce Media reports that 53% of Google’s entries were marked as confidential, leading to widespread criticism from industry analysts.
• October 2020: Google expands support to AdSense and AdMob, allowing individual publishers to choose between "Confidential" and "Transparent" status.
• August 2025: IAB Europe releases a study finding a 79% alignment between ads.txt and sellers.json, highlighting significant progress but persistent data quality issues.
• September 2026: The IAB Tech Lab’s Programmatic Governance Council releases "Programmatic Best Practices 1.0," signaling a renewed push for file maintenance as the industry grapples with aging standards.

Supporting Data and Quality Metrics

Despite its importance, the efficacy of sellers.json is often hampered by inconsistent data hygiene. A 2023 diagnostic from HUMAN Security noted that the consistency between declared supply chains and published sellers.json data stood at only 50%, marking it as one of the weakest links in the programmatic security chain.

Furthermore, the "confidentiality" loophole remains a point of contention. While the specification allows for entities to hide their identities for privacy reasons, buyers have frequently used this as a red flag. In 2020, for example, the ad tech company Centro took the drastic step of blocking intermediaries that failed to provide transparent entries, demonstrating how buyers have turned these public files into a core condition of trade.

The data is not only used for ad-buying decisions; it has become a resource for third-party analysts and even SEO practitioners. Because sellers.json files are publicly crawlable, they are frequently mined to identify high-performing niche websites, effectively turning the transparency tool into a market intelligence database.

Official Responses and Industry Governance

The IAB Tech Lab continues to manage the standard, though it has resisted major structural updates to the file format, keeping it at version 1.0 for over seven years. The recent focus has shifted toward "governance." By framing the standard within a broader "three-question" framework—who may sell, who the seller is, and how the request traveled—the Tech Lab is attempting to keep the ecosystem aligned without the need for a major, disruptive version update.

Google, as the largest player in the space, has had to balance the privacy of its massive base of individual publishers with the transparency demands of enterprise buyers. By allowing individual AdSense users to choose their transparency level, Google has attempted to mitigate privacy concerns, though this has resulted in a fragmented data landscape where "confidential" entries are common among smaller creators.

Implications for Marketers and Publishers

For marketers, sellers.json is the definitive reference layer for Supply Path Optimization (SPO). When a DSP receives a bid request, it performs an "offline" lookup against cached versions of these files. If the supply chain nodes do not align with the published records, the buyer can lower the bid, flag the inventory, or drop the request entirely.

In 2025, the stakes were raised further when Google’s DV360 introduced a seller ID blocklist, charging a 1.5% premium for tools that leverage sellers.json data to filter out suspicious supply paths. This effectively monetized the transparency standard, proving that in the modern programmatic age, "clean" data is a marketable commodity.

For publishers, the implications are equally significant. A publisher that fails to maintain accurate records—or that relies on resellers who provide incomplete information—risks being filtered out by the increasingly sophisticated automated buying systems of major brands. The "hidden" cost of non-compliance is the loss of demand from high-quality buyers who prioritize supply-chain hygiene.

The Limitations of Self-Declaration

The central, unavoidable weakness of sellers.json is that it relies on self-declaration. There is no cryptographic signature verifying that the data within the file is true. An SSP, if it were so inclined, could theoretically mislabel a reseller as a direct publisher.

Furthermore, the classification system is blunt. The "BOTH" category, which allows an entity to be both a publisher and a reseller, offers little clarity to a buyer trying to understand the nature of the impression. It also does nothing to address content quality; a "Made for Advertising" (MFA) site can provide a perfectly accurate and transparent sellers.json entry, meaning the file verifies identity, not integrity.

Conclusion: A Maturing Ecosystem

As we look toward 2027, the question facing the industry is whether a seven-year-old, static file format can continue to sustain the weight of a multi-billion-dollar programmatic economy. While the emergence of initiatives like The Trade Desk’s "OpenAds" suggests that the industry is looking beyond sellers.json for solutions to supply-chain manipulation, the file remains the baseline.

For now, sellers.json is no longer a "differentiator" for ad tech companies—it is "baseline hygiene." The era of blind programmatic trading is effectively over, replaced by a system where identity, mapping, and verification are the price of entry. Whether through stricter IAB governance or the eventual migration to a cryptographically signed standard, the industry’s commitment to transparency is unlikely to wane, even as the tools to achieve it continue to evolve.