Debug runbooks
When something in the header-bidding stack misbehaves, start here. Each runbook is a guided decision tree: answer one question at a time and it walks you to a root cause and a fix. Grounded in real Prebid, OpenRTB, and supply-chain mechanics.
Inspect a live page
Paste any URL. We load it in a real headless browser and read its actual header-bidding setup, Prebid, bidders, timeout, identity, schain, GAM, then flag any bidder live on the page but missing from the domain's ads.txt. Dev tools, fired from the app.
No bids
An ad unit gets zero bids, or one bidder never responds.
Walk from "is the auction even running" down to the specific reason a bidder returns nothing: consent gating, an authorization gap in ads.txt, a floor set above live demand, or a misconfigured adapter.
Timeouts / slow page
Bids arrive late or get dropped, or the header auction slows the page.
Trace latency from the budget you gave the auction (bidderTimeout, failsafeTimeout) through identity auctionDelay and slow individual adapters, deciding whether to widen the budget or prune the cost.
ads.txt mismatch / partner not spending
A partner is live but not spending, or buyers are not bidding through a path.
Diagnose why authorized-looking supply is not transacting: a missing or unauthorized ads.txt line, a DIRECT/RESELLER type mismatch against sellers.json, or an incomplete schain that buyers reject.
Not sure which runbook fits? Paste what you are seeing and you get a first-pass diagnosis: likely root causes, a fix, and what to check next. Nothing is stored.