sellers.json Confidentiality: The Revenue Cost SSPs Don't See

The is_confidential field in sellers.json was designed for a legitimate purpose: protecting the identity of sellers who have a business reason for privacy. Large publishers negotiating exclusive deals. Companies in industries where competitor intelligence matters. Entities with contractual confidentiality requirements.

In practice, it's become the default setting for thousands of seller entries that have no business reason to be hidden. And it's costing SSPs money they don't even realize they're losing.

Here's the mechanism. When a seller entry is marked confidential in your sellers.json, DSPs can see the seller_id but not the name, domain, or seller_type. The DSP receives a bid request, checks your sellers.json, finds the seller_id, and hits a wall. The identity is hidden. The verification chain breaks.

The DSP now has to make a choice: bid on inventory it can't fully verify, or skip it and move to a path where verification is complete.

Increasingly, DSPs skip it.

How Confidentiality Breaks Verification

The supply chain verification system has two sides. Publishers declare authorized sellers in ads.txt. SSPs confirm seller identities in sellers.json. DSPs check both.

When everything works:

1. Publisher's ads.txt says: ssp-x.com, 12345, DIRECT
2. SSP's sellers.json says: seller_id "12345", name "Publisher Inc", domain "publisher.com", seller_type PUBLISHER
3. DSP matches both sides. Verification passes. Bid proceeds.

When the entry is confidential:

1. Publisher's ads.txt says: ssp-x.com, 12345, DIRECT
2. SSP's sellers.json says: seller_id "12345", is_confidential: 1
3. DSP finds the seller_id but can't verify the identity, domain, or relationship type
4. Half the verification is missing. DSP can't confirm who this seller actually is.

The DSP knows the publisher authorized seller 12345. But it doesn't know if seller 12345 is actually the publisher (as the DIRECT label claims) or someone else. The seller could be the publisher. It could be a reseller using the publisher's account. It could be a fraudulent entry. The DSP simply can't tell.

The SPO Penalty

Supply path optimization is how DSPs decide which SSPs get their budget. SPO algorithms evaluate every supply path on multiple factors. Transparency is one of the heaviest weighted.

When a DSP runs SPO analysis on your platform and sees that 35% of your sellers are confidential, it calculates: 35% of the bid requests from this SSP will have incomplete verification. That's a transparency gap the DSP factors into its ranking.

SSPs with lower confidentiality ratios get higher transparency scores. Higher transparency scores mean higher SPO rankings. Higher rankings mean more DSP spend routed through your platform.

The math is direct. An SSP at 10% confidential has 90% of its bid requests fully verifiable. An SSP at 40% confidential has only 60% fully verifiable. If a DSP is choosing between two similar SSPs, the one with 90% verifiable inventory wins every time.

What the Data Shows

BeamFlow monitors sellers.json files across 2,000+ SSPs. The confidentiality patterns we see:

Industry average: Around 20-25% of entries are confidential across all SSPs we track.

Top-performing SSPs (those with the highest overall sellers.json health scores): Typically below 10% confidential. Some major SSPs run as low as 3-5%.

Underperforming SSPs: 40%+ confidential is common in the bottom quartile. Some SSPs have 60-70% of their entries marked confidential.

The correlation between confidentiality ratio and overall sellers.json health score is strong and negative. As confidentiality goes up, the health score goes down. This isn't because we arbitrarily penalize confidentiality. It's because high confidentiality ratios correlate with other data quality issues: stale entries, missing fields, and poor ads.txt alignment.

SSPs that don't invest in reducing confidentiality also tend not to invest in updating domains, fixing seller_type mismatches, or removing inactive accounts. The confidentiality ratio is often a proxy for overall file maintenance quality.

Why SSPs Default to Confidential

There are four common reasons SSPs end up with high confidentiality ratios, and most of them aren't deliberate:

1. Implementation Defaults

When SSPs first implemented sellers.json, some defaulted all entries to confidential as a safe starting point. The thinking: we'll make everyone non-confidential later, after we've communicated with publishers.

"Later" never came. The default stuck. Publishers were never asked about their preference. Years of new accounts were onboarded with the same confidential default.

2. Overcautious Legal Review

Legal teams sometimes recommend blanket confidentiality to avoid potential disclosure issues. This is usually overly cautious. The IAB Tech Lab spec was designed for public disclosure of seller identities. The information revealed (company name, domain, relationship type) is basic business information, not trade secrets.

3. Publisher Confusion

Some SSPs ask publishers during onboarding whether they want their account to be "visible in sellers.json." Without context, publishers choose privacy. If the question were framed as "Do you want DSPs to fully verify your inventory, or should we hide your identity (which may reduce your bid opportunities)?" the answer would be different.

4. Competitive Concerns

SSPs worry that making seller entries non-confidential reveals their publisher roster to competitors. This is a legitimate concern, but sellers.json only reveals that a publisher sells through your platform, not the commercial terms, not the volume, not the revenue share. And the trade-off (lower DSP trust, reduced SPO scores) typically costs more than the competitive intelligence it protects.

The Revenue Impact

Quantifying the exact revenue impact of confidentiality is difficult because DSPs don't publish their SPO scoring rubrics. But the directional impact is clear.

Reduced bid opportunities: DSPs that require full verification skip confidential seller entries. Every skipped bid is a potential transaction your platform lost.

Lower auction pressure: When fewer DSPs participate in an auction (because some skipped the confidential entry), the remaining bidders face less competition. Less competition means lower clearing prices. Lower prices mean less revenue for the publisher and less margin for the SSP.

SPO consolidation losses: When a DSP runs SPO analysis and decides to reduce the number of SSPs it buys through, platforms with high confidentiality ratios are more likely to be cut. This isn't a gradual decline. It's a step-function drop in demand.

Trust score degradation: DSPs that maintain internal trust scores for SSPs factor in transparency metrics. High confidentiality reduces your trust score, which affects bid behavior even for your non-confidential sellers. The DSP may bid less aggressively across all your inventory because the platform-level trust score is lower.

The aggregate effect: an SSP running at 40% confidential is likely leaving 10-20% of potential demand on the table compared to a similar SSP running at 5% confidential. That's not revenue the SSP sees and loses. It's revenue that never arrives. The bid requests go out, but fewer DSPs respond, and those that do bid less aggressively.

How to Reduce Confidentiality

The good news: reducing confidentiality is one of the simplest improvements an SSP can make. No new infrastructure. No specification changes. No publisher integration work.

Step 1: Audit Current State

Pull your sellers.json file and calculate your confidentiality ratio. How many entries are confidential? What percentage is that?

Step 2: Identify Low-Risk Conversions

Categorize your confidential entries:

• No documented reason for confidentiality: These can likely be switched immediately
• Default confidentiality from implementation: Contact these publishers. Most will consent to non-confidential status
• Publisher-requested confidentiality: Keep these confidential but document the business reason
• Contractual requirements: Keep these confidential until contracts can be renegotiated

In most SSPs, the first two categories cover 60-80% of confidential entries.

Step 3: Communicate with Publishers

For publishers where you want to switch from confidential to non-confidential, send a clear communication:

Explain what sellers.json is. Explain that confidential status limits DSP verification. Explain that switching to non-confidential can improve their bid opportunities. Ask for explicit consent (or at minimum, no objection within 30 days).

Most publishers consent because the value proposition is clear: better verification means more DSP trust means more potential revenue.

Step 4: Update in Batches

Don't switch all entries at once. Update in batches over 2-4 weeks. This gives you time to catch any issues (publisher complaints, unexpected data quality problems) before completing the rollout.

Step 5: Change the Default

This is the most important step. Change your onboarding flow so new accounts default to non-confidential. Confidentiality should be the exception that requires a documented reason, not the default that requires effort to override.

Frequently Asked Questions

Is there a legal requirement to mark sellers as confidential?

Generally, no. The information in sellers.json (company name, domain, relationship type) is basic business information. There may be specific jurisdictions or contracts that require confidentiality, but these are exceptions. Consult your legal team about your specific situation, but blanket confidentiality for all sellers typically isn't legally required.

Will publishers complain if I make them non-confidential?

Some might. But in our experience, the vast majority of publishers don't know they're marked confidential and don't care either way. The ones who might object are usually large publishers with specific privacy concerns. Handle those individually. For everyone else, a clear communication explaining the benefit of non-confidential status is sufficient.

How quickly will I see the impact of reducing confidentiality?

DSPs re-crawl sellers.json files regularly (daily to weekly for most major DSPs). Once they pick up the changes, the improved verification rates should translate into more complete SPO evaluations. The revenue impact builds over weeks to months as DSP algorithms adjust.

Can I make a seller non-confidential without their permission?

This depends on your terms of service and any specific agreements with the publisher. Some SSPs include a clause in their standard terms allowing them to list seller information in sellers.json. Others don't. Check your contracts and, when in doubt, ask for consent.

What's a good target for confidentiality ratio?

Below 10% is excellent. Below 20% is good. Above 30% means you're likely leaving meaningful demand on the table. The goal should be to get confidentiality as low as possible while respecting the legitimate privacy needs of specific publishers.