ca-pub- Extractor · GPT Network Codes · Header-Bidding Wrapper Detection

Publisher Monetization Header, AdSense & GPT Tag Inspector

Paste any page's <head> or HTML snippet to extract 16-digit pub- IDs, verify adsbygoogle.js attributes, detect Google Ad Manager / Prebid wrappers, and jump straight into reverse domain lookup.

1-Click HTML Samples:
Reverse AdSense Lookup Browse /id Directory

Map Extracted Publisher IDs & Run 30-Section Site Case Studies

Click any extracted pub- ID above to pivot into Publisher Domains (/id) or validate companion seller files in Reverse AdSense Lookup. Want source-linked product, traffic, and monetization analysis on any domain? Grab the $19 Starter Pack (120 non-expiring credits · 24 reports) or Pro ($49/mo · 400 credits).

What a Page's Ad Tags Reveal About Its Monetization Stack

Inspecting raw HTML headers alongside public ads.txt records lets publishers debug their own ad-tag hygiene and helps acquisitions/research teams identify how a site actually monetizes:

  • adsbygoogle.js & google-adsense-account Meta Tag: Confirms direct AdSense integration and verifies single async loading with crossorigin="anonymous".
  • Google Publisher Tag (gpt.js) Slot Paths: Extracts the numeric Google Ad Manager network code from googletag.defineSlot('/networkCode/adUnit') calls.
  • Managed Wrapper Signatures: Identifies Prebid.js, Amazon Publisher Services (apstag.js), Mediavine, Raptive, Ezoic, or Freestar scripts operating above AdSense backfill.

Tag inspection provides technical diagnostic guidance, not a Google approval guarantee.

Frequently Asked Questions

Should adsbygoogle.js be loaded more than once per page?

No. Include the async adsbygoogle.js script once inside <head> and trigger individual ad units with (adsbygoogle = window.adsbygoogle || []).push({}) calls.

What does the google-adsense-account meta tag do?

Google AdSense lets publishers verify site ownership without injecting live Auto Ads scripts by placing <meta name="google-adsense-account" content="ca-pub-16digits"> inside <head>.

Why do some sites contain multiple pub- IDs in HTML source?

Sites running managed header-bidding partners alongside an owned AdSense account may expose both the publisher's own ca-pub- seat and a partner MCM seat—every active seat must appear in /ads.txt.

How can I see other domains using an extracted pub- ID?

Click any extracted pub- link in the summary card above to open PubSpy's /id reverse publisher directory or run a full 30-section domain report.