Business & tax

Ad request coverage calculator

Measure matched-request coverage using the correct request denominator.

Your numbers

Calculated on your device. Your inputs aren’t sent to us.

Your result

Ready when you are

Enter your inputs and select Calculate.

Try it, understand it

Explore the result

Use matching request counts to compare coverage cases.

Worked example comparison
ExampleOutputWhat to notice
No requests matchedRequest coverage0%With 10,000 total requests and none matched, coverage is 0%.
8,000 requests matchedRequest coverage80%8,000 of 10,000 requests gives 80% request coverage.
Every request matchedRequest coverage100%10,000 of 10,000 gives 100% coverage, without saying whether the returned ads were viewable.

Check your understanding

Before checking: does impressions divided by page views give request coverage?

No. You need the matched-request count and total request count for the same scope.

Can a matched request create more than one impression?

Request-level coverage counts that request once when it returns at least one ad. Impression metrics have a different counting basis.

Behind the numbers

How this calculation works

Use request counts for a matching reporting scope. A request returning several impressions still counts once as a matched request. The complement identifies requests that returned no ad; it is not a measure of whether rendered ads were actually viewable.

THE FORMULACoverage = matched requests / total requests × 100%

A worked example

8,000 matched requests from 10,000 requests gives 80% coverage and 2,000 unfilled requests.

Good to know

A transparent arithmetic model using your inputs. Example prices, rates and multiples are demonstrations, not benchmarks or offers. No tax, exchange-rate conversion, live account access or automatic attribution is supplied. Monetary display is rounded; calculations retain additional precision.

A little curiosity

A request is not an impression or a page view

One page can make several ad requests. A matched request can return at least one ad, while the resulting impression count can use another reporting unit. Coverage is based on matched requests divided by total requests for the same scope.

Dividing ad impressions by page views cannot reconstruct this percentage when request counts are missing. It also cannot tell you whether an ad was visible on screen. Those questions require the appropriate reporting fields.

The ad revenue funnel separates request coverage, impressions per matched request and revenue per thousand impressions instead of treating them as interchangeable ratios.

Compare matching reporting scopes

Use the same dates, property, request type and reporting filters for the two counts. Mixing a site-wide numerator with a single-unit denominator can make an apparently extreme result that is simply a scope mismatch.

Zero matched requests with positive requests gives zero coverage. Zero total requests leaves the ratio undefined, so that input is rejected. A percentage describes what happened to those requests; it does not identify the cause of an unfilled request.

A few questions, answered

Can matched requests exceed requests?

Not for a properly matched request-level scope. The calculator rejects that combination and asks you to check the inputs.

Does 100% coverage mean 100% viewability?

No. Returning an ad and having it viewable on screen are different events and metrics.

Find your calculator

Start typing to explore the library.