Console Errors & Debugging

How to read the [advlume] console log — every key lifecycle message explained, the network request checklist, how to enable verbose debug mode, and browser extension conflicts to watch for.

The Advlume wrapper logs its entire lifecycle to the browser console using the [advlume] prefix. This article explains how to read these logs and what each message means.

Enabling verbose logging

By default, the wrapper logs key lifecycle events at the info level. To enable full debug output, add the following to the browser's console while the page is open:

localStorage.setItem('advlume_debug', '1');
location.reload();

To disable: localStorage.removeItem('advlume_debug').

Key log messages and their meanings

Message	Meaning
`[advlume] Config loaded for site {uuid}`	The site config was fetched from CDN successfully. Auction can proceed.
`[advlume] Config fetch failed`	CDN config could not be loaded. Ads will not serve. Check for network errors.
`[advlume] No slots found`	No `data-advlume-slot` divs were found in the DOM at init time.
`[advlume] Active bidders: ...`	List of demand partners that will participate in the auction for this page load.
`[advlume] ADMD score: 1 — High Risk`	Traffic quality gate has blocked this session. No ads will serve.
`[advlume] prebid.js failed to load`	Prebid library failed to load. Running in GAM-only mode (AdX direct, no header bidding).
`[advlume] Prebid timeout`	Some bidders did not respond within 1,500ms. Auction completed with available bids.
`[advlume] GAM targeting for {slotId}: ...`	Prebid price bucket targeting has been set on the GPT slot. Creative render is imminent.
`[advlume] Refresh slot {slotId} (refresh #N)`	Smart refresh triggered for the slot. N is the refresh count (max 10).
`[advlume] SPA: discovered N new slot(s)`	MutationObserver found new slots after initial load (SPA route change or dynamic content).
`[advlume] Loading hb-video.js`	Video module is being loaded because a video or outstream slot was found.

Network tab checklist

In the Network tab, check for:

cdn.advlume.com/hb.js — 200 OK
cdn.advlume.com/{site-uuid}.json — 200 OK (site config)
cdn.advlume.com/prebid.js — 200 OK
securepubads.g.doubleclick.net/tag/js/gpt.js — 200 OK
Prebid bid requests to *.adnxs.com, *.rubiconproject.com, etc. — should return within 1,500ms
WebSocket connection to advlume.com:6001 — status 101 (switching protocols)

Any of these returning non-200 or timing out indicates where the chain is breaking.

Common browser extension conflicts

uBlock Origin / AdGuard: Block the wrapper and all ad creatives. Always test in a clean profile without extensions.
Privacy Badger: May block the Socket.IO connection or the CMP script.
Ghostery: May block Prebid bid requests to specific DSPs.

Console Errors & Debugging

Enabling verbose logging

Key log messages and their meanings

Network tab checklist

Common browser extension conflicts

Further reading