AdSense Multiplex: New ad request counting
Starting June 23, 2026, Google AdSense will change how ad requests for Multiplex ad units are counted in reports. Multiplex formats display several native ads in a grid layout and are among the highest-earning placements for many publisher sites. Until now, one Multiplex block counted as a single ad request while each visible tile in the grid was recorded as its own impression. Going forward, Google will report every ad within the grid as a separate ad request. For operators of blogs, news sites, and niche portals, this is not a cosmetic tweak but a shift in core monetization metrics.
Multiplex ads are attractive for Google and publishers because they bundle multiple creatives in one compact module. Users scroll through a grid of recommendations styled to resemble editorial content. For AdSense accounts, that often means higher visibility per page view and additional revenue opportunities below the main article. At the same time, the previous counting logic was unintuitive for many analyses: one request produced multiple impressions, which distorted fill rate, request-based RPM, and internal dashboards whenever teams compared metrics without context.
What changes in the counting logic
Previously, the flow worked roughly like this: one Multiplex block on a page triggered one ad request. If the grid showed four visible slots, that produced one request and four impressions. From the effective date of June 23, 2026, AdSense will report four separate ad requests for the same scenario while still recording four impressions. Impressions per page view therefore stay the same, but counted requests rise in proportion to the number of slots in the grid. Anyone who interpreted reports at request level will see significantly higher request numbers after rollout even if actual ad delivery on the page does not necessarily change.
Google justifies the update with more transparent reporting. Each individual ad in the Multiplex grid represents its own delivery and therefore its own economic unit. The old logic bundled those units at request level and made direct comparison with other AdSense formats harder, since request and impression often correlate one to one elsewhere. For publishers with heavy Multiplex usage, the change can break historical trend lines because prior-year values and benchmarks are no longer directly comparable without adjustment.
Impact on key publisher metrics
Metrics that use requests in the denominator are especially affected. Fill rate, calculated as the ratio of served impressions to requested ad calls, may decline even though the actual delivery rate per slot has not worsened. Request-based RPM also shifts because revenue can stay flat while request volume rises. Teams tracking RPM per thousand requests internally must review formulas and alerts. Impression-based RPM values remain more stable as long as delivery and earnings do not change.
| Metric | Previously with Multiplex | From June 23, 2026 |
|---|---|---|
| Ad requests | 1 per Multiplex block | 1 per ad in the grid |
| Impressions | 1 per visible slot | Unchanged: 1 per slot |
| Fill rate (request-based) | Often artificially high | Closer to other formats |
| RPM (request-based) | Often lower than expected | Rises mathematically at same revenue |
Why this matters for SEO and content teams
Publishers monetizing organic traffic with AdSense often tie content performance to revenue per page view. When reporting foundations change, editorial and SEO meetings risk misinterpretation. An article with stable traffic may suddenly show weaker request-based values even though impressions and earnings stay flat. SEO leads should clearly separate organic ranking visibility from monetization metrics. AdSense changes do not affect rankings, but they influence how teams assess the economic value of templates and placements.
Comparison between Multiplex and classic display or in-article formats is especially sensitive. After the update, request counts align more closely with actual slot delivery. That simplifies portfolio analysis but requires a new baseline for internal targets. Anyone running A/B tests on ad positions should plan test windows so they do not cross the June 23, 2026 cutoff if request metrics are the primary success measure.
Practical steps for publishers
AdSense account holders should document existing reports and automated analyses before rollout. Exports from the AdSense dashboard, Looker Studio connections, and internal data warehouse pipelines need review if they use ad requests as a primary metric. Where possible, parallel tracking of impression-based RPM helps cushion trend breaks. Teams with multiple AdSense properties should monitor the change per property because Multiplex share varies strongly by vertical.
- Archive historical request data before June 23, 2026 as a reference.
- Shift dashboards toward impression RPM and total revenue as stable lead metrics.
- Recalibrate fill rate alerts to avoid false warnings after the cutoff.
- Document Multiplex slots per template to explain request jumps mathematically.
- Inform editorial and SEO stakeholders that this is a reporting change only.
API users pulling AdSense reports programmatically should review release notes and field definitions in Google AdSense reporting. Changes to request counting can affect aggregations in custom BI tools even when raw data fields look unchanged. A short test run after the cutoff with a limited date window helps detect deviations early and adjust mapping rules in ETL jobs.
For many sites the immediate business effect stays manageable as long as impressions and CPC earnings remain stable. The real challenge is interpretation: Multiplex will soon reflect the same economic reality as other formats, only with more granular request transparency. Publishers already steering on impressions and revenue mainly need to update communication and dashboards. Teams relying heavily on request-based efficiency metrics must redefine formulas, benchmarks, and targets before June 23, 2026.
