DSPs are cutting supply paths. Is your sellers.json one of them?
Buyers consolidate to fewer, cleaner SSPs. Your sellers.json accuracy determines whether you make their short list. We audit yours against 362K+ publisher ads.txt and app-ads.txt records.
Tracks 362K+ publisher domains. Instant analysis. Free.
Comprehensive Audit
A sellers.json audit that goes beyond structure.
File Structure & Completeness
Contact info, valid seller_type values, JSON formatting, seller ID uniqueness, and domain field accuracy.
Publisher Verification
Every seller entry cross-referenced against 362K+ publisher ads.txt and app-ads.txt records. We check if publishers actually authorize you.
Confidentiality Analysis
What percentage of sellers are marked "confidential"? DSPs penalize high-confidentiality SSPs. See how you compare to industry benchmarks.
The Buyer Perspective
Buyers verify every path. Mismatches mean lost bids.
Supply Path Optimization (SPO) is how DSPs choose which SSPs to buy from. They verify every supply path against ads.txt, app-ads.txt, and sellers.json. If your sellers.json doesn't match what publishers declare, DSPs route spend elsewhere.
High confidentiality rates signal opacity. Missing publisher verifications signal incomplete data. Both reduce buyer trust and limit your share of programmatic spend.
sellers.json entry
"seller_id": "pub-12345",
"seller_type": "PUBLISHER",
"domain": "example.com"
}
publisher ads.txt
sellers.json entry
"seller_id": "pub-67890",
"seller_type": "PUBLISHER",
"domain": "news.com"
}
The 5 sellers.json problems that cost SSPs demand.
High confidentiality rate
Marking sellers as “confidential” hides identity from DSPs. Industry trend is toward transparency. High rates = lower buyer trust.
Missing or wrong domain fields
The domain field should match the publisher’s actual domain. Mismatches cause verification failures across the ads.txt and app-ads.txt ecosystem.
Stale seller entries
Publishers who left your platform months ago still listed. Creates phantom supply paths that fail ads.txt verification.
seller_type mismatches
sellers.json says PUBLISHER but publisher’s ads.txt says RESELLER, or vice versa. Verification fails on every DSP.
Duplicate or conflicting entries
Same seller ID listed twice with different data. Strict DSPs may reject both entries.
How BeamFlow analyzes your sellers.json.
Fetch
We fetch your sellers.json from your domain.
Parse
Every seller entry parsed: seller_id, seller_type, domain, confidentiality status.
Cross-reference
Each seller verified against 362K+ publisher ads.txt and app-ads.txt records.
Report
Health score, verification sub-scores, confidentiality analysis, competitive benchmarks.
sellers.json analyzer FAQ
Enter your SSP domain above. BeamFlow fetches your sellers.json and audits every seller entry against 362K+ publisher ads.txt and app-ads.txt records.
A composite score: file completeness, seller verification rate, confidentiality ratio, structural accuracy. Higher = better buyer trust signals.
Confidential entries hide seller identity from DSPs. Some legitimate uses, but high rates signal opacity. DSPs prefer transparent supply paths for SPO.
DSPs choose shortest, most verified paths. Your sellers.json is a primary data source. Inaccurate data means DSPs route spend to competitors.
Ideally daily. Every time a publisher joins, leaves, or changes status, sellers.json should reflect it. Stale data creates verification failures.
Identifies the seller's role: PUBLISHER (direct), INTERMEDIARY (reseller), or BOTH. Must match the publisher's ads.txt (DIRECT = PUBLISHER, RESELLER = INTERMEDIARY).
Yes. Publishers can enter their SSP's domain to check if they're correctly listed. Helps diagnose unverified ads.txt and app-ads.txt entries.
Basic audit is free, no signup. For monitoring, publisher tracking, and competitive intel, see the SSP Intelligence plan at $499/mo.
See how DSPs evaluate your sellers.json.
Free audit against 362K+ publisher domains. Instant results.