Google’s 2027 Ad Impression Update: Why Publishers Need to Prepare Now
Have you checked your Google Ad Manager reports lately? If you haven’t paid attention to upcoming changes, you might be in for a rude awakening.
On February 17, 2027, Google is overhauling how it counts display ad impressions across AdSense and Ad Manager. Your total reported impressions are likely to drop, and if your site isn’t technically prepared, your ad revenue could take a serious hit along with them.
That sounds like a measurement change, and it is. But there is a practical consequence for publishers: the performance of the ad stack between the initial request and the point of rendering will become much more important. If an ad is slow to load and doesn’t render before the user leaves, that impression will no longer count.
Let's paint a clearer picture of what this looks like in practice.
From Download to Render
For years, Google has used a Count-on-Download (COD) methodology for display ads. An impression is recorded when the ad creative begins downloading to the user’s device, regardless of whether the creative ultimately renders.
Under the new Begin-to-Render (BTR) standard, an impression is only counted after the ad has successfully loaded and started rendering on screen. Google is making the change to align display measurement more closely with standards already used for video and native ads. The update applies to display banner inventory across desktop web, mobile web and CTV environments, and while publishers don’t need to make a manual technical integration for the change itself, it could have massive financial implications.
Imagine a user clicks a link to your article. The page starts loading, and the ad server instantly fires a request, initiating the download of an ad creative. But the user realizes they clicked the wrong link and hits the “back” button within two seconds. The ad never saw the light of day, but under the current COD model, you just recorded an impression. This has been the standard for years, masking underlying latency issues.
Also Read: In the AI era, brands need to be recommended, not just found
What happens to the impressions that don’t render?
Google expects publishers’ reported display impressions to decline as a result of the change. Because BTR is a stricter measurement standard, those “ghost” impressions, where users scroll past an ad before it loads, will vanish from reports.
That isn’t necessarily a problem in itself - an impression that was counted under COD but never actually rendered was always of limited value to the buyer. The bigger issue is understanding how large that gap is on a particular site and what is causing it.
A page can have a healthy impression count while still losing inventory between the ad request and the render. Heavy ad scripts, long bidder chains, unnecessary wrappers and poorly configured lazy loading can all add latency. So can the basic complexity of the page.
This also puts more focus on the relationship between ad loading and user behavior. A creative that takes several seconds to render on a page where users are leaving quickly is unlikely to generate the same value as one that appears while the user is still engaged with the page.
What publishers should measure now
Google has made comparative metrics available in Ad Manager for data after August 12, 2026. That gives publishers an opportunity to establish the size of the gap before the new methodology takes effect.
Start by comparing standard impressions with the new ad server BTR impressions metric. The difference gives you a baseline for how much inventory is currently being counted before it renders.
Audit ad loading
Look at the path from ad request to creative render. Identify unnecessary wrappers, heavy buyer scripts and bidder dependencies that add latency. In doing so, you will also improve the user experience, as editorial and advertising content will load more quickly.
Review lazy-loading configuration
If you use lazy loading, adjust fetch margins - the buffer zone above or below the current screen view. If the fetch margin is set too tight, the ad will not render until the user has already scrolled past the blank space it should occupy. Ads must be called early enough to fully render by the time users scroll them into view.
Look at bidders and layout
Not every source of latency will show up in a conventional page-speed score. A bidder that regularly fails to respond, a wrapper that adds another dependency, or a layout that leaves an ad below the point where users typically scroll can all affect whether an impression reaches the render stage.
What changes on February 17?
For those who don’t act now, the immediate effect of Google’s change will be a reduction in reported impressions for inventory that downloads but never renders. With the change still several months away, publishers have time to understand where that gap exists and address the parts of the ad stack that are causing it.
But while there is time to act, there’s no time to waste. Publishers need to ensure their ad density and load speeds are perfectly balanced to maximize render rates before the deadline - and they can’t afford to leave their yield to chance.
TDV edit UK version:
Google’s 2027 ad impression update: why publishers need to prepare now
Have you checked your Google Ad Manager reports lately? If you haven’t paid attention to upcoming changes, you might be in for a rude awakening.
On 17 February 2027, Google is overhauling how it counts display ad impressions across AdSense and Ad Manager. Your total reported impressions are likely to drop, and if your site isn’t technically prepared, your ad revenue could take a serious hit along with them.
That sounds like a measurement change, and it is. But there is a practical consequence for publishers: the performance of the ad stack between the initial request and the point of rendering will become much more important. If an ad is slow to load and doesn’t render before the user leaves, that impression will no longer count.
Let's paint a clearer picture of what this looks like in practice.
From Download to Render
For years, Google has used a Count-on-Download (COD) methodology for display ads. An impression is recorded when the ad creative begins downloading to the user’s device, regardless of whether the creative ultimately renders.
Under the new Begin-to-Render (BTR) standard, an impression is only counted after the ad has successfully loaded and started rendering on screen. Google is making the change to align display measurement more closely with standards already used for video and native ads. The update applies to display banner inventory across desktop web, mobile web and CTV environments, and while publishers don’t need to make a manual technical integration for the change itself, it could have massive financial implications.
Imagine a user clicks a link to your article. The page starts loading, and the ad server instantly fires a request, initiating the download of an ad creative. But the user realises they clicked the wrong link and hits the “back” button within two seconds. The ad never saw the light of day, but under the current COD model, you just recorded an impression. This has been the standard for years, masking underlying latency issues.
What happens to the impressions that don’t render?
Google expects publishers’ reported display impressions to decline as a result of the change. Because BTR is a stricter measurement standard, those “ghost” impressions, where users scroll past an ad before it loads, will vanish from reports.
That isn’t necessarily a problem in itself - an impression that was counted under COD but never actually rendered was always of limited value to the buyer. The bigger issue is understanding how large that gap is on a particular site and what is causing it.
A page can have a healthy impression count while still losing inventory between the ad request and the render. Heavy ad scripts, long bidder chains, unnecessary wrappers and poorly configured lazy loading can all add latency. So can the basic complexity of the page.
This also puts more focus on the relationship between ad loading and user behaviour. A creative that takes several seconds to render on a page where users are leaving quickly is unlikely to generate the same value as one that appears while the user is still engaged with the page.
What publishers should measure now
Google has made comparative metrics available in Ad Manager for data after August 12, 2026. That gives publishers an opportunity to establish the size of the gap before the new methodology takes effect.
Start by comparing standard impressions with the new ad server BTR impressions metric. The difference gives you a baseline for how much inventory is currently being counted before it renders.
Audit ad loading
Look at the path from ad request to creative render. Identify unnecessary wrappers, heavy buyer scripts and bidder dependencies that add latency. In doing so, you will also improve the user experience, as editorial and advertising content will load more quickly.
Review lazy-loading configuration
If you use lazy loading, adjust fetch margins - the buffer zone above or below the current screen view. If the fetch margin is set too tight, the ad will not render until the user has already scrolled past the blank space it should occupy. Ads must be called early enough to fully render by the time users scroll them into view.
Look at bidders and layout
Not every source of latency will show up in a conventional page-speed score. A bidder that regularly fails to respond, a wrapper that adds another dependency, or a layout that leaves an ad below the point where users typically scroll can all affect whether an impression reaches the render stage.
What changes on 17 February?
For those who don’t act now, the immediate effect of Google’s change will be a reduction in reported impressions for inventory that downloads but never renders. With the change still several months away, publishers have time to understand where that gap exists and address the parts of the ad stack that are causing it.
But while there is time to get ahead of the change, there’s no time to waste. Publishers need to ensure their ad density and load speeds are perfectly balanced to maximise render rates before the deadline - and they can’t afford to leave their yield to chance.
