Key Takeaways

• sellers.json transforms programmatic supply chains from opaque to verifiable. Before sellers.json, DSPs had no way to confirm who the actual seller was behind a bid request.
• Trust is built through identity verification, not just authorization. ads.txt says who is authorized. sellers.json confirms their identity. Together they give buyers the confidence to bid aggressively.
• Higher trust translates directly to higher CPMs. DSPs bid more on inventory from fully verified supply chains because they carry lower fraud risk.
• Confidential entries and missing sellers.json undermine trust. When sellers hide their identity or SSPs lack sellers.json, DSPs can't verify the chain and reduce their bids accordingly.
• The trend toward mandatory transparency is accelerating. Major DSPs increasingly require sellers.json for full supply chain verification before bidding.

---

How sellers.json Improves Supply Chain Trust

Programmatic advertising has a trust problem.

A bid request passes through multiple intermediaries before reaching a DSP, and at each step the buyer has to trust that the entity in the chain is who they claim to be. For years, that trust was based on contracts and relationships. There was no technical mechanism for a DSP to independently verify the identity of every seller in the supply path.

sellers.json changed that. It gave DSPs a machine-readable way to check the identity of every entity that touches a bid request. And that single capability reshaped how buyers evaluate and price programmatic inventory.

The Trust Gap Before sellers.json

Before sellers.json existed, DSPs relied on two things to evaluate supply quality: their own relationship with the SSP and the publisher's ads.txt file.

ads.txt told buyers which SSPs were authorized to sell a publisher's inventory. But it said nothing about the actual identity of the seller account behind the transaction.

This created a specific vulnerability. A bad actor could set up an account on a legitimate SSP, claim to represent a premium publisher, and sell spoofed inventory. The DSP would check ads.txt, see the SSP listed, and assume the bid was legitimate. The SSP was authorized. The account behind it was not verified.

The industry lost billions to this kind of domain spoofing and inventory fraud. The authorization layer existed. The identity layer did not.

How sellers.json Fills the Gap

sellers.json is maintained by SSPs and exchanges, not publishers. Each SSP publishes a file at https://ssp-domain.com/sellers.json that lists every seller on their platform. For each seller, the file includes:

• seller_id: The account identifier (matches the account ID in publishers' ads.txt)
• name: The business name of the seller
• domain: The seller's website domain
• seller_type: PUBLISHER (direct inventory owner) or INTERMEDIARY (reseller)
• is_confidential: Whether the seller's identity is hidden

This is the identity verification layer. When a DSP receives a bid request, it can now check ads.txt to confirm authorization and sellers.json to confirm identity. The seller_id in the bid request maps to a real business name and domain. The DSP can verify that the entity selling CNN inventory is actually CNN, not an unknown account claiming to be CNN.

The Verification Chain in Practice

Here's how the trust chain works when a DSP evaluates a bid request:

Step 1: Authorization check. The DSP reads the publisher's ads.txt file. It confirms the SSP and account ID are listed as authorized sellers.

Step 2: Identity check. The DSP reads the SSP's sellers.json file. It looks up the seller_id from the bid request and checks the name, domain, and seller_type.

Step 3: Consistency check. The DSP verifies that the domain in sellers.json matches the domain in the bid request. If the bid claims to be from nytimes.com, the sellers.json entry for that seller_id should show nytimes.com as the domain.

Step 4: Supply chain validation. Using the SupplyChain object (schain) in the bid request, the DSP traces every node in the chain. Each node's seller_id can be verified against the corresponding SSP's sellers.json.

When all four steps pass, the DSP has high confidence that the inventory is legitimate. This confidence translates directly into bidding behavior.

Trust and CPM Impact

DSPs use supply chain verification as a pricing signal.

Inventory with full verification gets higher bids because it carries lower fraud risk. Inventory with verification gaps gets discounted or excluded entirely.

The math is straightforward. If a DSP's fraud detection model estimates that 5% of unverified supply is fraudulent, they discount bids on all unverified supply to account for that risk. The legitimate publishers in the unverified pool lose revenue because of the bad actors they're grouped with.

Fully verified supply chains break publishers out of that risk pool. When a DSP can independently confirm the publisher's identity through sellers.json, the fraud risk drops to near zero for that specific path. The bid increases accordingly.

Industry data suggests that fully verified supply paths see 10-30% higher CPMs compared to partially verified paths. The exact premium varies by DSP and vertical, but the direction is consistent. More verification means more trust means higher bids.

What Breaks Trust

Several common issues undermine the trust that sellers.json is designed to create.

Missing sellers.json Files

Some SSPs still don't maintain a sellers.json file. When a DSP encounters an SSP without sellers.json, the entire identity verification step fails. The DSP can't verify any seller on that platform. This affects every publisher using that SSP, not just the ones with issues.

Confidential Entries

When an SSP marks a seller as confidential (is_confidential: true), the name, domain, and seller_type are hidden.

The DSP sees that a seller_id exists but can't verify who it belongs to. From the DSP's perspective, a confidential entry is barely better than a missing entry. The identity verification step fails either way.

BeamFlow's data shows that approximately 15% of sellers.json entries across the ecosystem are marked confidential. Each of those entries represents a publisher whose identity can't be verified by buyers.

Stale Data

When an SSP doesn't update sellers.json regularly, previously valid entries become incorrect. A publisher might change their domain, an account might be reclassified, or new accounts might not be added for weeks. Stale data creates false verification failures for legitimate publishers and false verification successes for accounts that should have been removed.

Mismatches Between ads.txt and sellers.json

When the data in a publisher's ads.txt doesn't match the corresponding sellers.json entry, the verification chain breaks.

The seller_id might be listed in ads.txt but missing from sellers.json. The domain might differ. The seller_type might conflict. Each mismatch is a point where DSP trust degrades.

BeamFlow's monitoring shows that 24% of ads.txt entries have some form of sellers.json verification failure. That's nearly a quarter of all programmatic supply paths operating with broken trust signals.

How to Maximize Supply Chain Trust

For Publishers

Verify all SSP entries. For each SSP in your ads.txt, check their sellers.json to confirm your account appears with correct details. Use BeamFlow's scanner to automate this.

Request non-confidential status. If any SSP lists you as confidential, contact them and request non-confidential status. There's no legitimate reason for most publishers to be confidential. Every confidential entry costs you trust and potentially CPMs.

Monitor quarterly at minimum. SSPs change their sellers.json without notification. An entry that verified correctly in January might be wrong in April. Regular monitoring catches drift before it compounds.

Choose SSPs with good transparency practices. SSPs that maintain accurate, complete, and frequently updated sellers.json files deliver better demand quality because buyers trust their platform more.

For SSPs

Maintain complete, non-confidential data. Every seller on your platform should have a complete, non-confidential entry in sellers.json. Missing or confidential entries reduce buyer trust in your entire platform, not just individual sellers.

Update frequently. Daily updates are the minimum. Real-time updates when seller data changes are ideal. Every hour of stale data creates verification failures for active publishers.

Validate accuracy. Implement automated checks that verify seller_ids are current, domains resolve correctly, and seller_type classifications match actual configurations.

The Trend Toward Mandatory Transparency

The industry is moving toward requiring sellers.json for bid eligibility.

Major DSPs have implemented or announced policies that deprioritize or exclude supply paths that can't be fully verified. This isn't a future possibility. It's happening now.

The IAB Tech Lab has strengthened sellers.json specifications. Industry groups are pushing for universal adoption. And the largest buyers in the ecosystem are encoding transparency requirements into their bidding algorithms.

For publishers, this means sellers.json verification is shifting from "nice to have" to "required for premium demand." For SSPs, it means maintaining sellers.json is shifting from "recommended practice" to "competitive necessity."

The supply chains that invested in full transparency early are already capturing the premium. The ones still operating with verification gaps are losing ground every quarter as buyer requirements tighten.

Frequently Asked Questions

Does sellers.json directly increase my CPMs?

Not directly. sellers.json enables DSPs to verify your identity, which increases their confidence in your inventory. Higher confidence leads to higher bids. The CPM increase comes from DSP bidding behavior, not from sellers.json itself.

What if my SSP doesn't have sellers.json?

Your inventory can't be fully verified by DSPs through that SSP. Consider whether the SSP's other qualities outweigh this limitation, and advocate for them to implement sellers.json.

How quickly do DSPs adopt sellers.json changes?

Most DSPs cache sellers.json data and refresh it every 24-72 hours. Changes to sellers.json entries may take a few days to be reflected in DSP bidding behavior.