Prebid can print the auction to the browser console. Use it on a page you are inspecting. Leave it off for readers.
Add pbjs_debug=true to the page URL. Prebid then logs auction messages and stops hiding JavaScript errors it would otherwise swallow so the rest of the page survives. Filter the console on MESSAGE:. The troubleshooting guide names three of them: calling a bidder, setting key-values, and renderAd when a Prebid line item actually wins the ad server.
pbjs.version is the build you are running. pbjs.getConfig() shows the timeout and price granularity in effect. pbjs.getAdserverTargeting() shows the hb_ keys Prebid intends to send, after the auction. pbjs.getBidResponses() and pbjs.getAllWinningBids() show who answered. Bids that missed the timeout are absent.
A permanent switch exists for a page that should always log. Prebid warns that debug mode makes Prebid Server return extra information, and that most server-side adapters then treat the request as a test and leave it off reports.
Prefer the query string for a single view. This config keeps debug on for every view of the page. Turn it off when you are done. The debugging module, which intercepts bids and substitutes a CPM, is a different feature and persists in session storage until you disable it.
pbjs.setConfig({ debug: true });You can see whether the auction ran, which bidder timed out, and whether GAM received hb_ keys before you touch a line item. renderAd in the console is the confirmation that a Prebid creative, not only a Prebid key, won.
Debug on a production page adds console work for every reader and can mark Prebid Server traffic as test. A targeting dump taken before the auction finishes is an empty answer, not a broken setup. Injected bids from the debugging module are not demand.
pbjs_debug.