Impressions and the viewability problem
An impression counts a piece of content being shown — a search result, an ad, a social post. The trap is that 'shown' has no single definition: Search Console counts a listing appearing in results, ad servers count an ad being delivered, and the IAB/MRC viewable-impression standard requires a portion of pixels visible for a minimum time before it counts. Impressions are only comparable within one definition.
What this means
An impression is one instance of content being presented. It is the denominator for click-through rate and the unit advertisers often pay against (CPM = cost per mille, per thousand impressions). The number is only as meaningful as the definition of 'presented' behind it.
The viewability problem
A served impression may load below the fold and never be seen. To address this, the IAB and MRC defined a 'viewable impression': for display, at least 50% of the ad's pixels in view for at least one continuous second (longer for video). Google Search Console, by contrast, counts an impression when your listing appears in results — with its own rules for paginated and lazy-loaded results. Because each system draws the line differently, cross-platform impression totals do not add up to a single audited exposure.
- Served impression: content delivered, not necessarily seen
- Viewable impression: 50% pixels, 1s (IAB/MRC display standard)
- Search Console: listing appeared in results, with its own rules
How it appears in analytics and logs
An impression count signals how much exposure something received. Whether those impressions were actually seen depends on the standard — a served impression may never have entered the viewport.
Diagnostic use case
Read impressions as exposure within a single platform's definition, and never sum or compare impressions across systems that define 'shown' differently.
What WebmasterID can help detect
WebmasterID can record first-party element-visibility events on your own pages, so on-site 'impression' counts use a definition you control rather than an opaque ad-server one.
Common mistakes
- Summing impressions across platforms with different definitions.
- Assuming a served impression was actually viewed.
- Comparing Search Console impressions to ad impressions.
Privacy and accuracy notes
Impressions are aggregate exposure counts, not records of individuals. Reporting an impression needs no personal identifier.
Related pages
- Click-through rate (CTR)
Click-through rate is clicks divided by impressions, expressed as a percentage. The catch is what counts as an impression: Google Search Console counts a result appearing in search, while ad platforms count an ad being served or viewed. Because the denominator differs by platform, CTR figures are only comparable within the same system — and a low CTR can mean wrong audience or simply low intent.
- Pageviews: what the metric counts
A pageview is recorded when a page is loaded (or a virtual page is rendered in a single-page app). It is the oldest web-analytics metric and the easiest to misread: pageviews count loads, not people, and modern apps and prefetching can inflate or hide them. This page defines the metric and its caveats.
- The scroll event and depth tracking
A scroll event records that a visitor scrolled to a depth on the page. In GA4 enhanced measurement, a single scroll event fires once per page when the visitor reaches 90% of the page height. It is a coarse engagement signal — useful for spotting content people do not reach, but limited because the default is one threshold, not a continuous read-depth curve.
- CTA tracking
Define on-site impressions with first-party events.
Sources and verification notes
- IAB/MRC — Viewable ad impression measurement guidelines
- Google — Search Console: clicks, impressions, CTR, position
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.