Skip to content
stated:methodYour own data, read and written up

Finding 04

US page views averaged under a tenth of India's ads per view

Ad impressions per page view ran at 0.072 for the United States, the property's second largest market by page views, against 0.97 for India and 1.19 to 2.42 for Canada, Australia, France and the UK. We do not know why.

In plain terms

On one site, about 7 ads were shown per 100 page views from the United States, against about 97 from India and 119 to 242 from Canada, Australia, France and the UK. Why is not known.

Published
Window
28 days, 2026-08-13 to 2026-09-09
Sample
19,485 ad impressions across 30,966 page views, 102 countries
Instrument
Google AdSense ads shown and page views by country, one site, one 28-day window.

This is a clear anomaly with no explanation, and it is reported as exactly that.

What was measured

Ad impressions divided by page views, by country, over one window. Where readers load pages and ads fill, the ratio lands somewhere near the number of ad slots on the page. India sits at 0.97, and Canada, Australia, France and the UK between 1.19 and 2.42. The United States, the second largest market by page views, sits at 0.072.

Ad impressions per page view by country, 28 days
CountryPage viewsAd impressionsPer view
Russia5300.000
United States11,6388420.072
Singapore6641000.151
India16,04315,6370.97
Canada, Australia, France, UK--1.19 to 2.42

What this comparison holds constant

It is one instrument, one metric pair, one window and one ad configuration, and the markup is identical on every page a reader in any country receives. What it cannot hold constant is the mix of pages each market read: the report gives each country a total, not a page by page count. So the gap is reported with no explanation attached to it. Finding 03 meets the same limit from the other side: its figures are per page, with no country split.

What it does not establish

Not the cause. At least four things produce this same signature and nothing measured here separates them.

  • Unfilled inventory. An ad request can return no ad, and our own operating notes for this property record unfilled slots as common on it.
  • Automated traffic. Requests that fetch the document and never run what comes after it. Suggestive here only because the three lowest ratios are cloud regions, which is a pattern and not a result.
  • Ad blocking. Adoption differs sharply by market, and a blocked slot and an unfilled one look identical in this ratio.
  • Page mix. A market that reads more of the pages carrying fewer ad slots averages fewer ads per view with nothing failing anywhere, and a country total cannot show which pages each market read.

A comparison we are not making

Search Console recorded 72 clicks from this market over the same window against 11,638 reported page views. Set side by side, that looks like a factor of 162 between two instruments. It is not a discrepancy.

The two numbers count different populations. Ad network page views include every acquisition channel, direct, referral, social and assistant traffic among them, and count several views within a single visit. Search Console counts clicks arriving from Google Search, once each. A site can legitimately report both figures with nothing disagreeing anywhere, so the ratio between them means nothing on its own.

It is set out here because it is an easy comparison to reach for, and it looks compelling.

What would actually settle it

Four things, in order, and none of them has been run.

  1. 01Ads per view by country and page together. Each market compared on the pages it actually read. This removes the page mix explanation or confirms it before anything else is spent.
  2. 02Ad request coverage. Requests against matched requests for that market. This measures fill directly, and it is the one that either removes the unfilled explanation or confirms it.
  3. 03Traffic validation at the log. User agents, request patterns and whether the page assets were ever fetched. Analytics cannot answer this, because a client that never runs the script never appears in it at all.
  4. 04Engagement time, as support only. It is not decisive. It measures focus for sessions that were recorded at all, brief genuine visits also produce very little of it, and ordinary engagement would not establish that inventory went unfilled.

Why it is worth reporting unresolved

Because the number is load bearing. Page views for this market were the largest non-domestic block on the property and were being read as an audience worth expanding toward. Whatever the cause, a market averaging under a tenth of India's ads per view is not a market anyone should size a plan against until the reason is known.

How to check your own

Pull ad impressions and page views by country for one month and divide, then rank ascending, and break any low market down by page before reading anything into it. A market an order of magnitude below your others is worth investigating, not discarding, and the ratio tells you where to look rather than what is there.

Then resist the comparison in the section above. Before setting two numbers against each other, check that they count the same population, over the same window, at the same granularity. The comparison above shares a window, fails on the other two, and still produces a figure that reads well.

Full method

Ad impressions and page views by country from AdSense reporting for a single window, divided. The same property, the same ad code and the same window across all 102 countries, so the comparison holds the instrument, the ad code and the window constant. It does not hold the mix of pages each market read: the report gives country totals, not pages.

Free toolsHow much of your report the query rows hold, and whether two periods line up on the calendar.Drop a Search Console export. Read in your browser, nothing uploaded.See the tools