Learn & Understand

Why the Viewability Standard Landed on 50% for 1 Second

The 50%-of-pixels-for-1-second viewability threshold this calculator's benchmark references wasn't picked arbitrarily - it was a deliberate industry compromise between a technically measurable standard and a genuinely meaningful definition of "seen."

Why Not Simply Require 100% of the Ad to Be Visible?

A stricter 100%-visible standard would exclude a large share of impressions that most reasonable observers would still consider genuinely seen - an ad with 90% of its area visible and only a small sliver cropped by the edge of a browser window is realistically still viewable to the person looking at the page, and a 100% threshold would have systematically undercounted this common, benign scenario. The Media Rating Council and Interactive Advertising Bureau, working through this tradeoff in the early-to-mid 2010s as the industry sought a shared standard, settled on 50% of pixels as a practical threshold that captured the reasonable middle ground between "technically rendered somewhere on the page" and "unambiguously fully in view."

Why a Duration Requirement Was Added at All

Pixel visibility alone doesn't distinguish an ad a user genuinely paused on from one that merely flickered into view for a fraction of a second during a fast scroll past a page - the 1-second continuous duration requirement (2 seconds for video, reflecting that video needs slightly longer to convey any message at all) exists specifically to filter out these fleeting, effectively meaningless exposures, requiring the ad to remain substantially visible for at least a brief, real moment before counting as a genuine viewable impression.

The Technical Measurement Problem the Standard Had to Work Around

Measuring on-screen pixel visibility accurately runs into a genuine technical obstacle: many ads are served inside iframes for security and cross-domain isolation reasons, and browser security models historically restricted an iframe's own JavaScript from directly querying its exact position and visibility on the surrounding page (a protection against malicious cross-site scripts snooping on unrelated page content). Viewability measurement vendors had to develop workaround techniques - safe-frame APIs, browser-provided visibility APIs, and various detection methods - specifically to measure something the platform's own security architecture was originally designed to prevent measuring directly, which is part of why different measurement vendors can report meaningfully different viewability rates for the exact same served impressions, depending on which workaround technique each vendor relies on.

Applying This When Comparing Viewability Figures

Because measurement technique varies by vendor, comparing viewability rates reported by two different measurement tools for the same inventory should be done cautiously - a meaningful discrepancy between vendors doesn't necessarily mean one is wrong, it may simply reflect different technical approaches to a problem that browser security architecture never made straightforward to measure directly in the first place.