Short answer: Google says AdSense display, mobile-web and CTV-banner inventory will move from count-on-download (COD) to begin-to-render (BTR) impressions on 17 February 2027; prepare a like-for-like baseline and render audit.
Google’s AdSense documentation frames this as an impression-definition switch, not a mandatory code migration. Publishers should know which inventory is affected, preserve a comparable baseline, and keep impression counts separate from revenue conclusions.
What changes on 17 February 2027
Google’s AdSense Help documentation says begin-to-render impressions will start for display web, mobile web and CTV banner inventory on 17 February 2027. Google also says no action is required to enable the change. That makes this a measurement-preparation task rather than a forced code migration.
The practical effect is that some publishers may see a lower impression count because an impression is counted later in the ad lifecycle. Google says the current count-on-download (COD) count starts when the ad begins downloading, while begin-to-render counts when the creative has loaded and starts rendering. A lower count is therefore not automatically proof of a traffic or revenue problem.
For the broader measurement discipline, connect the work to the YouTube engaged-views reporting guide and Search Console AI reporting. The metric definitions differ, but the operating principle is the same: name the event before comparing it.
| Current COD | Count-on-download: the ad starts downloading, according to Google. |
|---|---|
| Future BTR | Counts when the creative loads and starts rendering. |
| Start date | 17 February 2027 for display web, mobile web and CTV banner inventory, per Google Help. |
| Publisher action | Google says no action is required to switch; measurement and render-path preparation are still useful. |
| Already BTR | Google says native, in-app and video inventory already use BTR and are BTR-compliant; the announced switch names display web, mobile web and CTV banner inventory. |
Build a clean baseline before the switch
Use the period before the change to export a baseline by property, inventory type, device and ad format. Google separately says Ad Manager publishers can use detailed reporting with specified dimensions and metrics, including historical data from 12 August 2026, to estimate the impact. That is an Ad Manager reporting recommendation, not a claim that every AdSense publisher has those tools. If the property is AdSense-only, use the dimensions and metrics actually exposed in its account and label the baseline accordingly.
Record COD impressions, BTR impressions where available, viewability or render diagnostics, revenue and page performance. Keep the time zone and reporting window explicit. If a property has multiple templates, separate them; a slow mobile template can move differently from a fast desktop article even when the account total looks stable. Do not assume that an Ad Manager dimension or metric exists in an AdSense-only view.
Do not manufacture a conversion between COD and BTR. They are different lifecycle events. A bridge table can show both counts and the ratio for a fixed slice, but the ratio is an observation for that slice, not a permanent multiplier.
- Export a pre-change baseline before 17 February 2027.
- Keep property, device, format and date dimensions stable.
- Store both COD and BTR where the report exposes them.
- Separate count movement from revenue, viewability and traffic movement.
- Annotate template, lazy-loading and creative changes alongside the data.
Audit the render path without breaking performance
Google’s guidance points publishers toward the creative download and render path. Check that the ad slot is requested at the intended time, that the creative can load on a representative mobile connection, and that the page gives the slot a sensible opportunity to render. Measure the result rather than assuming a single configuration is best.
Lazy loading can reduce unnecessary work but can also delay an ad that is too close to the viewport. A large render margin may increase network and device work. The right setting depends on the page and audience, so document the test and watch Core Web Vitals, user experience, fill, revenue and the new impression definition together.
Use the on-page SEO checklist for page-quality checks and the AI for Google Ads guide only for adjacent paid-media context. Neither page should be treated as an AdSense implementation authority.
| Creative | Check load size, format and render behavior on representative devices. |
|---|---|
| Slot timing | Test when the slot is requested and how close it is to the viewport. |
| Lazy loading | Balance unnecessary work against a timely render; do not remove it blindly. |
| Page quality | Watch performance and user experience while investigating monetization metrics. |
| Evidence | Keep before/after test settings and dates with the reporting extract. |
How to explain a lower impression count
When the definition changes, start the explanation with the count event. If BTR is later than COD, some impressions that previously counted at download may no longer count because the creative did not reach the render stage. That is a measurement change. It does not, by itself, say whether the user’s page view or the advertiser’s outcome changed.
Then inspect the render funnel: ad request, response, creative download, start of render, viewability and downstream revenue. Compare like with like. A revenue change needs its own analysis of demand, format mix, geography, seasonality, policy and page experience; do not turn a secondary article’s assumption into a forecast.
For a related platform-metric example, the target CPA and ROAS changes guide shows why an event-definition change should be documented before performance is interpreted.
Publisher checklist
By the time February 2027 arrives, the important work is a clean record, not a frantic site-wide rewrite. Confirm which inventory is affected, capture the pre-change baseline, audit the render path, and prepare a dashboard or spreadsheet that can display COD and BTR side by side.
After the switch, annotate the first reporting period, compare the same properties and templates, and escalate only when the render funnel or revenue evidence shows a material issue. Keep Google’s Help page as the source of truth for the definition and date, because secondary coverage can age faster than the product documentation.
Recommended workflow
- Inventory the affected display web, mobile web and CTV banner placements.
- Export a stable COD/BTR baseline and label the reporting window and dimensions.
- Audit creative load, slot timing and lazy-loading trade-offs on representative devices.
- On or after 17 February 2027, compare like-for-like counts and render-funnel evidence.
- Separate impression-definition changes from revenue conclusions and document any follow-up test.
Related Digital Marketer guides
- YouTube engaged-views reporting — A comparable platform measurement change.
- Google Search Console AI Performance Reports — Measurement and visibility reporting context.
- Google Ads target CPA and ROAS changes — Paid-media measurement and bidding context.
- Google AI Max exact-match prioritization — Existing Google AI Max owner; avoid cannibalising it.
- AI for Google Ads guide — Paid-search automation context.
- on-page SEO checklist — Rendering and page-quality implementation context.
Questions marketers are asking
Do I need to change AdSense code before February 2027?
Google’s Help page says no action is required for the switch. A baseline and render-path audit are still sensible preparation.
Will AdSense impressions definitely fall?
Google says they may decrease because BTR is counted later than COD. The size and business effect are property-specific and not forecast here.
What inventory is affected?
Google names display web, mobile web and CTV banner inventory for the 17 February 2027 switch. It says native, in-app and video inventory already use BTR and are BTR-compliant.
Can I use COD as a conversion factor for BTR?
Use a fixed-slice ratio for observation, not a permanent multiplier. The events represent different stages of the ad lifecycle.
Sources and dates
Publication, event, and update dates are kept separate below. A source without a stated publication date is marked accordingly; access date is 2 September 2026.
- Google AdSense Help: Begin-to-render impressions — published/event date: not stated; accessed 2 September 2026. Google says display web, mobile web and CTV banner inventory will switch on 17 February 2027; it defines COD and BTR and separately describes detailed historical-report guidance for Ad Manager publishers.
- Search Engine Land: AdSense begin-to-render context — published/event date: 2026-09-01; accessed 2 September 2026. Secondary discovery only; Google Help controls the timeline and definitions.
Editorial note: Re-check platform documentation immediately before implementation. Product rollouts, eligibility, pricing, policy, and measurement definitions can change after this draft.
