IAB Sellers.json v1.0 · Google Realtime Bidding Transparency · Supply-Chain Auditor

Sellers.json Lookup, Google Seller Checker & IAB Validator

Enter any pub-16digits ID to inspect its expected Google Realtime Bidding sellers.json structure and live connected domains, or paste any IAB sellers.json JSON payload to audit seller_type, is_confidential bid-shading warnings, and ads.txt supply-chain mismatches.

1-Click Calibration Presets:

Accepts a 16-digit pub- / ca-pub- ID, a full IAB sellers.json document ({"version":"1.0","sellers":[...]}), a JSON array of seller entries, or a single seller JSON object (up to 512 KB / 2,000 entries).

Paste lines from the target domain's /ads.txt (including optional OWNERDOMAIN=) to verify that DIRECT vs RESELLER declarations align with PUBLISHER vs INTERMEDIARY seats.

Reverse AdSense Lookup Browse /id Directory

Turn Seller IDs into Verified Multi-Domain Competitive Intelligence

Once you validate a publisher's seller_id, jump to PubSpy Publisher Domains (/id) to see live websites declaring that Google ID in public ads.txt files (first 2 lookups open; free email OTP unlocks full tables & CSV exports). Need deep commercial teardowns? Unlock the $19 Starter Pack (120 non-expiring credits · 24 structured 30-section domain reports) or run continuous research on Pro ($49/mo · 400 credits).

Publisher & AdOps Guide to IAB sellers.json, Google Seller Visibility, and Supply-Path Audits

Modern programmatic advertising relies on three interlocking IAB Tech Lab transparency standards to authenticate every impression from publisher page to demand-side platform (DSP): ads.txt / app-ads.txt hosted on the publisher's root domain, the OpenRTB SupplyChain (schain) object passed inside real-time bid requests, and sellers.json v1.0 hosted by every SSP and ad exchange.

While ads.txt lets a website declare "I authorize account X on exchange Y to sell my ad inventory," only the exchange's own sellers.json file reveals who legally owns account X, what corporate domain belongs to that account, and whether that account is a direct media publisher or an intermediary reseller. When those two files disagree—or when a publisher leaves their seat hidden behind confidential defaults—programmatic buyers routinely apply bid-shading discounts or exclude the inventory from high-CPM brand campaigns.

1. Inside Google's realtimebidding.google.com/sellers.json Feed

Google publishes its consolidated AdSense, AdMob, and Google Ad Manager (AdX) seller directory at https://realtimebidding.google.com/sellers.json, which HTTP-redirects to Google Cloud Storage at https://storage.googleapis.com/adx-rtb-dictionaries/sellers.json. Two engineering realities shape how publishers and analysts work with Google's file:

  • Massive file footprint & CORS policy: Because Google's global feed indexes millions of active publisher seats in a single multi-hundred-megabyte JSON payload without permissive browser cross-origin headers, ordinary web tabs cannot stream the raw file directly. Instead, ad-ops engineers inspect individual pub-16digits expectations, stream-filter the dictionary via CLI (curl -sL + jq/grep), or cross-reference observed publisher domains in PubSpy /id.
  • Seller ID normalization: Inside Google's sellers.json, every AdSense publisher seat uses "seller_id": "pub-XXXXXXXXXXXXXXXX" (16 digits, never ca-pub-), paired with Google's root TAG-ID f08c47fec0942fa0 in the document's top-level identifiers array.

2. Confidential (is_confidential: 1) vs Transparent (is_confidential: 0) in Google AdSense

By default, newly created Google AdSense accounts often start with seller visibility set to Confidential. When Confidential mode is active, Google emits "is_confidential": 1 in sellers.json and strips both your legal name and your business domain from the public feed.

Although Confidential mode is spec-compliant under IAB v1.0, Supply-Path Optimization (SPO) engines operated by major agency trading desks and DSPs treat anonymous seller seats with caution. Without a visible domain field in sellers.json, a buyer cannot confirm that the OWNERDOMAIN declared in your ads.txt file matches the legal entity receiving ad payouts.

How to switch Google AdSense to Transparent: Sign in to Google AdSense, navigate to Account → Settings → Account information → Seller information visibility, switch the radio option from Confidential to Transparent, and enter your verified root business domain (bare hostname such as example.com without https:// or trailing slashes). Google propagates updated seller records into its next daily Realtime Bidding dictionary snapshot.

3. Decoding Every IAB sellers.json v1.0 Field

Whether you are auditing a boutique header-bidding SSP, an MCM parent partner, or a pasted Google seat snippet, our deterministic validator inspects six core attributes defined by the IAB Tech Lab specification:

  • seller_id (Required String): The exact exchange-assigned account identifier that must match Field 2 of the corresponding ads.txt record and the asi/sid node in OpenRTB schain.
  • seller_type (Required Enum): Must be uppercase PUBLISHER (ad revenue paid directly to the inventory owner), INTERMEDIARY (account resells inventory it does not own), or BOTH (hybrid networks monetizing both owned-and-operated sites and third-party partner sites).
  • is_confidential (Integer 0 or 1): Defaults to 0 when omitted. Must be encoded as an integer—not boolean true/false—so strict C++/Go RTB parsers do not reject the entry.
  • name & domain (Required when Transparent): When is_confidential equals 0, the exchange must disclose the legal entity's name and its registrable root business domain (without protocol schemes or URL paths).
  • is_passthrough (Optional Integer 0 or 1): Indicates technical routing seats (such as certain SaaS ad-server wrappers) where buyer spend passes straight through to downstream seller seats rather than terminating commercially at the passthrough entity.

4. Catching DIRECT vs INTERMEDIARY Supply-Chain Contradictions

One of the highest-impact monetization bugs uncovered during site acquisitions and ad-stack audits is unauthorized DIRECT spoofing. Unscrupulous or misconfigured ad networks occasionally instruct publishers to paste google.com, pub-XXXXXXXXXXXXXXXX, DIRECT, f08c47fec0942fa0 using the network's own brokerage seat rather than the publisher's seat.

When you paste both the seller entry and the site's ads.txt lines into the cross-checker above, PubSpy immediately flags two red-flag mismatches:

  1. DIRECT + INTERMEDIARY Conflict: Claiming DIRECT in ads.txt when the exchange's sellers.json labels that seller_id strictly as INTERMEDIARY violates IAB supply-chain rules and causes anti-fraud filters to drop bids. Third-party reseller seats belong under RESELLER.
  2. OWNERDOMAIN Drift: Declaring OWNERDOMAIN=brand-a.com in ads.txt while your primary DIRECT seat publishes "domain": "unrelated-entity.io" in sellers.json signals broken corporate domain alignment unless documented via MANAGERDOMAIN.

5. From sellers.json Verification to Portfolio Discovery

Auditing sellers.json tells you how an exchange classifies a publisher ID; pairing it with public ads.txt graph data reveals the publisher's actual footprint on the web. After confirming a pub- seat above, click straight into PubSpy Publisher Domains (/id) or Reverse AdSense Lookup to inspect other domains sharing that exact seller ID, check their seller hygiene in our Ads.txt Validator, and model traffic monetization scenarios in the AdSense Revenue & Valuation Calculator.

All validations on this page rely strictly on deterministic IAB specification rules and observable public declarations. Supply-chain cleanup improves programmatic buyer trust, while AdSense site approval and auction eCPMs remain governed by Google's policy review and real-time advertiser demand—treat these diagnostics as operational publisher guidance, never an approval guarantee.

Sellers.json Lookup & Validator FAQ

Where is Google's official AdSense and AdX sellers.json file hosted?

Google hosts its live dictionary at https://realtimebidding.google.com/sellers.json (redirecting to https://storage.googleapis.com/adx-rtb-dictionaries/sellers.json). You can manage your own seat inside Google AdSense under Account → Settings → Account information → Seller information visibility.

Should I set Google AdSense Seller information visibility to Transparent or Confidential?

Most commercial publishers choose Transparent (is_confidential: 0) so DSPs can verify their legal entity name and match their business domain against OWNERDOMAIN in ads.txt, avoiding anonymous-seat bid shading.

What causes a DIRECT vs INTERMEDIARY mismatch between ads.txt and sellers.json?

Listing a third-party network's account as DIRECT in your ads.txt when the exchange's sellers.json classifies that seat as INTERMEDIARY creates a supply-chain contradiction. Only accounts you directly own (PUBLISHER or BOTH) should be marked DIRECT.

What are the three valid seller_type values in IAB sellers.json v1.0?

Exactly three uppercase strings are valid: PUBLISHER (direct media owner), INTERMEDIARY (reseller/mediation partner), and BOTH (accounts operating owned sites alongside resold third-party inventory).

Does switching sellers.json to Transparent guarantee higher revenue or AdSense approval?

No. Transparent metadata removes verification friction for programmatic buyers, while actual CPMs and site approvals depend on Google's policy review, audience quality, and advertiser demand. All PubSpy tools provide diagnostic guidance, not a Google approval guarantee.