AdSense Unmatched Requests or Coverage: Which Metric?

Searchers type unmatched ad requests when a breakdown table shows a gray (Unmatched ad requests) row. Others type Coverage when they want the fill percentage column in Reports. Both belong to the same request-matching story—how often an ad request returns an ad—but they answer different reading jobs in the AdSense UI.

This page routes only. It does not re-teach Help’s full Coverage formula or every breakdown report—that stays on the owners below.

Early owners:

• AdSense unmatched ad requests basics
• AdSense Coverage report basics for small blogs
• AdSense Coverage or Fill Rate: Which Metric?
• AdSense ad requests vs impressions basics
• AdSense ads not showing: what to check

Coverage column = sitewide or filtered fill percentage. Unmatched row = accounting for asks that returned no ad in a breakdown. Confused about requests versus impressions → ad-requests owner. Blank units on a live page → ads-not-showing after you confirm the metric story moved.

Official Help: Coverage · Unmatched ad requests · Troubleshoot ad coverage issues. AdSense is a Google product; report labels change over time.

Disclosure: Metric router only. No niche fill benchmarks, RPM forecasts, or invented account examples.

Table of contents

1. Two lenses on the same gap
2. When Coverage is the right first open
3. When unmatched rows are the right first open
4. Reading order on a worried afternoon
5. Sibling metrics this page is not
6. Mistakes worth avoiding
7. FAQ
8. Close the router and open one owner

Two lenses on the same gap

Google counts an ad request each time your ad code asks for an ad—even when nothing comes back. Coverage compresses that story into one percentage in Reports:

Coverage = (Ad requests that returned ads ÷ Total ad requests) × 100

When Coverage is below 100%, some requests are unmatched. Help documents unmatched requests separately because breakdown reports need a bucket for “asked, got nothing”—not because unmatched is a penalty label.

Mechanism beginners miss: unmatched rows are not underperforming contextual ads. Help warns you cannot treat unmatched requests like failed contextual placements; there was no ad to classify. That is why CashPilot keeps an unmatched owner distinct from Coverage reading—even though both numbers move together when fill falls.

When Coverage is the right first open

Open Coverage report basics when your job looks like:

• You are in Reports hunting the Coverage column under Advanced metrics
• You need Help’s official percentage before debating forum synonyms
• Earnings moved and Google’s troubleshooting order says to read pageviews, then coverage, then impressions
• You want calm date windows on a small blog so one thin day does not fake a crisis

Coverage answers: Across this slice and range, what share of requests returned an ad? It is the headline fill statistic—not Page RPM, not click rate, not “how much money.”

If your search was literally “fill rate” wording rather than the Coverage column, check Coverage vs fill rate for vocabulary routing before you open two owners at once.

When unmatched rows are the right first open

Open unmatched ad requests basics when your job looks like:

• A table shows (Unmatched ad requests) beside Ad unit, Targeting types, or similar breakdowns
• You wonder why a row exists on a “healthy” account
• You need Help’s example where three units ask and one returns nothing—producing one unmatched request
• You are tempted to merge unmatched volume into contextual versus placement analysis

Unmatched answers: Which asks in this breakdown never received an ad? It is row-level accounting inside specific reports, not the single Coverage percentage on the summary line.

One mistake beginners make is staring at an unmatched row, then blocking categories as if Google classified a bad contextual ad. If I were sequencing a first monthly review, I would read Coverage on a 7–28 day window, then open unmatched breakdowns only if I need to know which units or slices drove the gap—not the other way around.

Reading order on a worried afternoon

Use this sequence when fill feels “off” but you are not sure which metric name brought you here:

1. Policy center and Sites status — serving restrictions change whether anything can match (not covered deeply here, but a two-minute glance prevents metric rabbit holes on a restricted site).
2. Coverage on a sensible range — did the percentage actually move versus last month?
3. Request chain sanity — if requests versus impressions is fuzzy, read ad requests vs impressions once.
4. Unmatched breakdown — if Coverage dropped, which report row shows unmatched volume; do not analyze unmatched as contextual performance.
5. Live page — if units are blank while Coverage looks fine on long windows, open ads not showing.

Google’s Troubleshoot ad coverage issues lists real-world drivers—ads.txt, blocking, policy limits, unit sizing, and more. Confirm against your account; forums love false single causes.

Sibling metrics this page is not

This URL does not invent a second Coverage formula from Analytics exports. Help’s Coverage definition is the official match percentage.

Mistakes worth avoiding

Chasing unmatched on hourly windows on a ten-pageview day. Small denominators exaggerate breakdown tables; prefer ranges once you understand the metric.

Treating unmatched as an error code. Unless Coverage collapsed alongside Policy warnings or visible blank inventory, unmatched rows can be normal arithmetic.

Rewriting the theme before reading Coverage. Low match can be technical or demand-side; confirm the request story before major content surgery.

Opening unmatched and Coverage owners simultaneously while editing ad code the same hour—pick one diagnostic lens, finish, then change placements or blocks.

FAQ

Are unmatched ad requests the opposite of Coverage?

They describe the same unfilled gap—Coverage as a percentage, unmatched as counted asks in breakdown reports. When Coverage falls, unmatched rows usually grow.

Which report shows Coverage as a column?

AdSense Reports with the Coverage Advanced metric. The Coverage report basics owner teaches reading habits; this page only routes.

Which reports show (Unmatched ad requests)?

Help lists breakdown reports such as Targeting types and Ad unit. The unmatched owner explains why those rows are not contextual performance.

Is this Coverage vs fill rate?

No. That sibling translates Coverage versus the phrase fill rate. This sibling translates Coverage versus the unmatched row.

Should I panic over unmatched rows?

Not by default. Investigate spikes with Coverage, Policy center, and live blank units—not every low-traffic day.

Coverage fell—what order should I use?

Coverage on a sensible window first, then unmatched breakdowns for slice detail, then ads-not-showing if the live page is empty.

Does this replace ads not showing?

No. Metric owners first when numbers moved; ads-not-showing when slots are blank on the URL you are testing.

Official documentation?

AdSense Help on Coverage, unmatched ad requests, and coverage troubleshooting—confirm live labels in your account.

Close the router and open one owner

Coverage is the Reports percentage for matched requests over total requests. Unmatched ad requests are the unfilled asks—often visible as their own breakdown row. They move together; they are not two competing formulas from different vendors.

Pick Coverage when you need the headline fill statistic and report habits. Pick unmatched when the UI surfaced the row and you need Help’s accounting rules. Pick ads-not-showing when the live page is empty after you confirmed the metric shift. This page should take under a minute—then work on the owner that matches how you searched.