Key Takeaways

• A missing sellers.json entry means DSPs can't verify the seller's identity. Your ads.txt authorization exists, but identity confirmation doesn't. DSPs treat this as an incomplete supply path.
• The revenue impact is silent. No error message. No declined bid notification. No alert from your SSP. Bids just don't arrive at full potential, or don't arrive at all.
• Missing entries have multiple causes. New accounts not yet added. SSP platform migrations. Data cleanup removing entries. Or SSPs that just don't maintain sellers.json.
• Publishers often don't realize entries are missing. Without active monitoring, the gap between expected and actual revenue gets blamed on market conditions instead of a technical verification failure.
• The fix needs SSP action, but you have to push for it. SSPs have little reason to proactively audit their sellers.json for completeness. You need to check and escalate.

---

Why Missing sellers.json Entries Hurt Monetization

Here's a scenario that plays out across thousands of publisher-SSP relationships every day.

A publisher has a properly formatted ads.txt file. Active account with an SSP. Ad requests flowing. Everything looks normal.

But the SSP's sellers.json file doesn't include the publisher's account. Or the account was removed during a platform migration. Or the SSP never added the entry after onboarding.

The publisher has no idea. Revenue is lower than expected, but there's no error message pointing to sellers.json. The missing entry is invisible to everyone except the DSPs who check it, and they respond by cutting bids or skipping the opportunity entirely.

How Missing Entries Create Revenue Loss

The programmatic verification chain needs two confirmations for full trust. First, ads.txt confirms the publisher authorized the SSP to sell their inventory. Second, sellers.json confirms the identity of the seller account on the SSP's platform.

When a sellers.json entry is missing, the second confirmation fails. The DSP's verification engine returns "seller not found" for that account ID. What happens next depends on the DSP's policy.

Conservative DSPs exclude the bid opportunity entirely. If the seller identity can't be verified, the DSP doesn't bid. The publisher never sees these potential bids in their reporting because the bid was never submitted.

Moderate DSPs submit a bid but at a big discount. The fraud risk model assigns a penalty to unverified supply paths. The bid price reflects that penalty. The publisher sees the impression fill but at a lower CPM than comparable verified inventory.

Permissive DSPs bid normally regardless of sellers.json status. These DSPs are becoming less common as the industry moves toward stricter verification.

The net effect is that a missing sellers.json entry reduces the number of bidders, reduces the bid prices from remaining bidders, or both. Your effective CPM drops without any visible cause.

Why This Damage Is Invisible

Most revenue analytics dashboards don't show sellers.json verification status. Publishers monitor fill rates, CPMs, and total revenue. When these metrics decline, the typical investigation looks at:

• Seasonal demand changes
• Advertiser budget shifts
• Ad format performance
• Floor price settings
• Header bidding configuration

sellers.json verification status is rarely on the checklist. The dashboard doesn't have a column for "bids lost due to failed identity verification." The SSP doesn't send an alert saying "your account is missing from our sellers.json."

This invisibility is what makes missing entries so damaging. The revenue leak can persist for weeks or months before anyone thinks to check whether the SSP's sellers.json includes the publisher's account.

Common Causes of Missing Entries

New Account Not Yet Added

The most common cause.

A publisher signs up with a new SSP, configures their ad server, adds the SSP to ads.txt, and starts serving impressions. The SSP's internal process for adding the account to sellers.json runs on a different timeline. It might take days. Weeks. In some cases, never happen without a specific request.

The publisher assumes onboarding is complete because ads are serving. They don't know the identity verification layer is missing.

Platform Migration

When an SSP migrates to a new platform, rebuilds their infrastructure, or merges with another company, sellers.json is often regenerated from the new system. Accounts that existed in the old sellers.json may not transfer correctly to the new one. Account IDs may change format. Some accounts may be dropped entirely.

These migrations are exactly when publishers should check their sellers.json entries, and exactly when they usually don't.

Data Cleanup

SSPs periodically clean their sellers.json to remove inactive or dormant accounts. The threshold for "inactive" varies by SSP. A publisher with low volume through a particular SSP might be removed during cleanup even though the relationship is still active.

SSP Does Not Maintain sellers.json

Some SSPs, particularly smaller or regional ones, don't maintain a sellers.json file at all. Every publisher on that SSP has a missing entry by definition. The entire platform's inventory operates with incomplete verification.

Entry Was Never Created

Some SSPs need a specific request or configuration step to add a publisher to sellers.json. If you don't know to request it and the SSP doesn't add it automatically, the entry just never exists.

Quantifying the Impact

The revenue impact of a missing sellers.json entry depends on several factors.

How many DSPs enforce sellers.json. As of 2025, the majority of major DSPs incorporate sellers.json verification into their bidding logic. The number is growing. An entry that was missing in 2023 might have had minimal impact. The same missing entry in 2025 affects a bigger portion of demand.

The publisher's vertical and CPM level. Premium inventory in high-CPM verticals like finance, health, and tech sees the biggest impact because DSPs apply stricter verification to higher-value bids. A missing entry on a $2 CPM ad unit matters less than one on a $15 CPM placement.

The specific SSP. If the missing entry is on a major SSP that channels big demand to you, the impact is huge. If it's on a minor SSP that accounts for 2% of revenue, the absolute dollar impact is smaller (though the percentage loss through that SSP is the same).

Competitive density. In header bidding setups where multiple SSPs compete for the same impression, losing bids from one SSP due to sellers.json issues shifts demand to other SSPs. You may see total revenue hold somewhat steady while one SSP underperforms. This makes the issue even harder to detect.

Industry analyses suggest that publishers with unresolved sellers.json issues lose between 5-20% of potential programmatic revenue across affected SSP paths. For publishers with multiple missing entries, the cumulative impact compounds.

How to Detect Missing Entries

Manual Check

For each SSP in your ads.txt:

1. Go to https://ssp-domain.com/sellers.json
2. Search for your account ID in the file
3. Verify the entry exists with correct name, domain, and seller_type

This works but doesn't scale. A publisher with 20 SSPs in their ads.txt needs to check 20 sellers.json files. Many of these files contain hundreds of thousands of entries.

Automated Monitoring

Use BeamFlow's scanner to automatically cross-verify all your ads.txt entries against sellers.json. The scanner checks every SSP in your ads.txt file and flags any missing entries, mismatches, or verification failures.

Automated monitoring also catches entries that disappear after initially being verified. An SSP data cleanup or migration can remove an entry that existed last month. Without continuous monitoring, you wouldn't know until the next manual audit.

How to Fix Missing Entries

Step 1: Identify the Gap

Run a full cross-verification of your ads.txt against all SSP sellers.json files. Document every SSP where your account is missing.

Step 2: Contact the SSP

For each missing entry, contact your account manager or SSP support. Provide:

• Your account ID (seller_id)
• Your business name
• Your publisher domain
• The relationship type (PUBLISHER for direct, INTERMEDIARY for reseller)
• Your ads.txt entry showing the SSP is authorized

Step 3: Request Specific Details

Ask the SSP:

• When will the entry be added?
• Will it be non-confidential?
• Will the domain field match your primary domain?

Step 4: Verify After Resolution

After the SSP confirms the entry is added, verify it yourself. Check that the seller_id, name, domain, and seller_type are all correct. An entry that exists but has wrong data creates different issues (mismatches rather than missing entries, but still verification failures).

Step 5: Set Up Monitoring

Set up ongoing monitoring so you catch any future removals or changes. Quarterly manual checks work as a baseline, but automated monitoring catches issues faster.

Frequently Asked Questions

How do I know if a missing sellers.json entry is costing me money?

You often can't tell from standard reporting. The bids that never arrive due to failed verification don't show up as "lost bids" in most SSP dashboards. The most reliable approach is to fix all missing entries and measure the before/after CPM change on that SSP.

What if the SSP doesn't have sellers.json at all?

If the SSP doesn't maintain sellers.json, all publishers on that SSP have unverified identities. Consider whether the SSP provides enough value to justify the verification gap, and push them to implement sellers.json.

Can I be listed in sellers.json without the SSP in my ads.txt?

Technically yes, an SSP can list you in their sellers.json regardless of your ads.txt. But without the ads.txt entry, DSPs will fail the authorization check even if the identity check passes. Both files need to be aligned.

How long does it typically take an SSP to add a sellers.json entry?

It varies wildly. Some SSPs add entries within 24-48 hours of a request. Others take weeks. A few need specific onboarding steps. Set expectations when you contact the SSP and follow up if the timeline passes.