An ad only counts as seen at all under one specific, industry-wide test: at least 50% of its area visible for at least one second for display ads, or at least two seconds for video, the Media Rating Council standard that Google's own Active View documentation confirms is still the measurement bar every major advertiser and exchange screens inventory against.

Above-the-fold placements average 68% viewability, while below-the-fold placements average 40%, and across the industry, nearly half of all display ads are never actually viewed at all. That gap does not show up as a single alarming number on a dashboard. It shows up as a site-wide average that looks acceptable while specific placements underneath it are quietly failing.

Advertiser spend on retail media alone is forecast to reach $71.09 billion in 2026, up from $60.32 billion in 2025, part of the broader climb in advertiser budgets heading into the holiday quarter. An impression that never becomes viewable is a bid that never had a chance to compete for that budget, and that cost is highest exactly when competition for gaming and entertainment audiences is climbing toward its yearly peak.

Why Your Site-Wide Viewability Average Hides Where the Losses Actually Are

A single average across an entire site can look fine while individual placements sit well below it. A long tier-list page or a wiki table that readers scroll through slowly behaves completely differently from a short news post that gets read top to bottom in twenty seconds. An ad unit placed the same way on both templates will not perform the same way on both.

Google's own Ad Manager reporting lets publishers segment "Active View viewable impressions" by ad unit and by device, not just as one number for the whole site. That segmentation is the actual audit. Pulling the site-wide average tells a publisher almost nothing useful. Pulling the same report broken out by placement and by page template tells them exactly where the problem lives.

The practical version of this at solo or small-team scale is a short, repeatable check rather than a full analytics project. Pull the ad-server report segmented by ad unit and device. Sort by viewability rate, low to high. Anything sitting at or near the 40% below-the-fold benchmark is worth a second look, especially on a page template that has not had its layout or ad placements reviewed since the last content redesign. A placement that was fine a year ago is not guaranteed to still be fine after a template change moved it further down the page.

Gaming and entertainment sites tend to run a handful of distinct templates rather than one uniform layout, and each one carries a different viewability risk. A patch-notes page or a short news post gets read start to finish quickly, which pulls lower units into view fast. A tier-list page, a build calculator, or a long wiki table keeps a reader scrolling slowly or not scrolling much at all past the point they found what they needed, which is exactly the layout where a mid-page or footer unit can sit unseen for most of a session. Auditing by template, not just by placement, catches this distinction that a single site-wide average cannot show.

This check takes less time than it sounds like it should. Most ad servers already collect this data. The only missing step for most publishers is looking at it segmented rather than as a single blended number, which is the number most dashboards show by default.

Matching Ad Format to Where Attention Actually Lands

Once a specific low-viewability placement is identified, the fix is rarely "remove the ad." It is usually "change what kind of ad unit sits there." Sticky vertical sidebar units average 80 to 90% viewability, and mobile anchor or footer units average 85 to 95%, because they stay in the viewport as the reader scrolls instead of disappearing the moment the page moves. That is a wide gap against the roughly 40% average for a static unit sitting below the fold.

The second lever is when the ad call actually fires. Google's own guidance confirms that lazy loading, holding an ad call until the unit is about to enter the viewport, reduces the number of impressions served completely out of view, which improves both viewability and page load speed at the same time. A static unit that loads the instant the page renders, regardless of whether anyone will ever scroll far enough to see it, is generating impressions that were never going to count as viewed in the first place.

For a publisher working through the placements flagged in the audit above, there are two concrete options rather than a long list of possibilities. Where the layout allows it, convert a chronically low-viewability static unit into a sticky or anchored format instead. Where a sticky conversion does not fit the page design, apply a lazy-load trigger so the ad call fires closer to the moment the unit will actually be seen, rather than the moment the page first loads. Neither change requires a rebuild. Both are adjustments to units that already exist on the page.

A sticky unit only helps if it stays out of the way of what the reader is actually there for. On a build calculator or a tool-heavy page, a sticky ad that overlaps an input field or a results table will cost more in frustrated users than it gains in viewability. The fix is placing a sticky unit only where no interactive content sits directly below it, which on most gaming and entertainment templates means a side rail or a bottom anchor rather than a unit stacked between sections of a page the reader is actively using.

Where This Shows Up on Nitro's Dashboard

If your site runs on Nitro, the audit in the first tactic does not require a separate analytics setup. Nitro's own dashboard lets publishers track their average viewability rate directly, which means the segmentation work described above starts from data you already have access to, not a new tool you need to configure.

Nitro's own placement data lines up with the external numbers above. We've identified that sticky anchor, side rail, and sticky stack ad units perform better across its network, the same pattern the sticky-format research above describes. Nitro also lets publishers enable lazy loading directly, recommended specifically for below-the-fold placements, along with a setting that only refreshes an ad when it is actually visible rather than on a blind timer.

The number worth knowing before Q4 specifically comes from our own data: viewability changes on a site with low viewability rates can increase CPM and RPM by up to two times the current rate. That lift does not happen instantly. Advertisers take time to notice a viewability improvement before adjusting their bidding, which is exactly why this audit is worth doing now rather than in November, once Q4 demand has already peaked and the adjustment window has narrowed. For publishers who would rather not run the audit themselves, Nitro also offers a managed placement service where the Nitro team determines and optimizes ad placement directly.

Nitro is dedicated to reinventing website monetization for the gaming industry. Our ad tech platform delivers uncompromised user experience alongside high performance revenue, with Net 7 payouts, same day support, and fully transparent real time reporting.