Ads Not Showing
Step-by-step troubleshooting for empty ad slots — check the console for [advlume] errors, verify the script is loading, confirm site approval status, disable ad blockers, and match slot keys exactly.
If your ad slots appear to be empty or the creatives are not rendering, work through this checklist in order. Most issues are caused by one of the common problems listed here.
1. Check the browser console for errors
Open DevTools (F12) and look at the Console tab. Advlume logs its entire lifecycle using the [advlume] prefix. Look for:
Config fetch failed— the site config could not be loaded. Check your internet connection, or contact support if the CDN is down.ADMD score 1 — blocking all ad rendering— the traffic quality score flagged this session as non-human. Try a different device or network.No slots found— the wrapper could not find anydata-advlume-slotdivs on the page. Check that your snippets are present in the page source.prebid.js failed to load— the Prebid library could not be fetched. Check network errors in the Network tab.
2. Verify the script tag is loading
In DevTools → Network tab, filter by "hb.js". The script should return a 200 OK with the correct Content-Type. If it returns 404, your script tag URL is incorrect — copy it fresh from the dashboard.
3. Check that slot divs are in the DOM
In DevTools → Elements tab, search for data-advlume-slot. Each slot should be visible in the page source. Common issues:
- The divs are inside a Vue/React component that hasn't rendered yet when the wrapper initialises. The SPA observer should catch them, but check whether they appear in the DOM at all.
- A caching plugin served a cached version of the page that pre-dates the snippet addition.
- The CMS stripped the HTML snippet because of a tag filter. Try pasting it in a Custom HTML block instead of the main content editor.
4. Verify your site is approved
Ads are not served on sites that are not yet approved. Check your site's status in the dashboard. If your site is pending review, you will not see ads until approval is granted.
5. Check ads.txt status
While a missing ads.txt does not prevent ads from rendering, some demand partners will suppress bids for inventory without a valid file. If ads are showing for some demand partners but not others, this may be the cause. See ads.txt Setup Guide.
6. Disable browser extensions
Ad blockers (uBlock Origin, AdGuard, Privacy Badger) will block the Advlume script and all ad creatives. Test in a private browsing window without extensions enabled to confirm ads serve correctly in a clean browser session.
7. Check that the slot key matches
The data-advlume-slot value must exactly match the slot key you created in the dashboard (case-sensitive). A typo (e.g. Leaderboard vs leaderboard) will cause the auction to run but GAM to have no matching ad unit for the slot path.
8. Wait up to 10 minutes after first setup
After a new site or ad unit is added, the GAM ad unit and line items need to propagate. Allow up to 10 minutes on a brand new setup before concluding that something is broken.
Further reading
- Console Errors & Debugging — reading the wrapper's full log output
- Low Fill Rate — ads are showing but empty too often
- ads.txt Errors in GAM — fixing demand suppression due to ads.txt issues
Last updated 2 months ago