Why Are Ad Requests Higher Than Impressions in Google Ad Manager?

For publishers and ad operations specialists, comparing ad requests with impressions is a useful way to understand ad delivery. A publisher may receive thousands of ad requests from its website or app but record fewer impressions in Google Ad Manager (GAM).

This difference can result from unfilled inventory, line-item eligibility, creative rendering problems, video playback issues, or differences in reporting definitions. The correct explanation depends on which metrics you are comparing and how the inventory is implemented.

1. What Is an Ad Request in Google Ad Manager?

An ad request is a request sent to an ad server or ad-serving system asking for an ad to be selected for a particular opportunity. On a webpage, a Google Publisher Tag (GPT) can send a request to Google Ad Manager when an ad slot is requested.

The request provides information that helps the system determine which ads may be eligible to serve. Depending on the setup, that information can include the ad unit, requested size, targeting values, page or app context, and other signals.

After receiving the request, GAM evaluates eligible demand and determines whether an ad can be returned. A request is therefore an early stage of the delivery process, not proof that an impression has been recorded.

2. What Is an Impression in Google Ad Manager?

An impression is an ad delivery event recorded according to the counting rules for the relevant ad product and format. It is the metric publishers commonly use to measure the volume of ads delivered.

However, the exact moment an impression is counted varies by inventory type. Display, mobile app, and video inventory can follow different impression-counting methodologies. A response from the ad server is not necessarily the same event as a recorded impression.

For this reason, it is important not to assume that every ad request should equal one impression or that every ad-server response will always produce a recorded impression.

3. Ad Request vs. Ad Response vs. Impression

These terms describe different stages of ad delivery. Understanding them makes GAM troubleshooting much easier.

These stages are related, but they should not be treated as interchangeable metrics. Some reports expose more detailed delivery stages than others.

4. Main Reasons Ad Requests Are Higher Than Impressions

Reason 1: Unfilled ad requests

One of the most common explanations is that some requests do not return an eligible ad. Google Ad Manager calls these unfilled impressions in its reporting terminology.

An unfilled impression means that an ad request did not return an ad because no line item was eligible to serve. This may happen when targeting, scheduling, inventory requirements, or available demand prevent an eligible ad from being selected.

For example, a publisher might have an ad unit requesting a 300 × 250 display ad, but no eligible line item or demand source returns an ad for that request.

Possible causes include:

• No eligible line items target the requested ad unit or size.
• Line items are outside their start or end dates.
• Targeting rules exclude the inventory.
• There is insufficient eligible demand to fill the opportunity.
• Price floors, blocking rules, or demand-side restrictions prevent available bids from competing.

How to investigate: Review unfilled impressions by ad unit and requested ad size. Then use GAM’s delivery troubleshooting tools to determine why eligible line items are not serving.

Official guidance: Troubleshoot unfilled impressions in Ad Manager.

Reason 2: The creative was served but did not render

An ad response or code-served event does not guarantee that the creative will render successfully. A visitor may leave the page before the creative loads, a device may have poor connectivity, or the creative may encounter a technical error.

In these cases, GAM may record an ad-serving event without recording the expected impression for the relevant format and measurement.

How to investigate:

• Review the line item’s Troubleshoot tab and non-delivery information.
• Compare code-served counts with impressions where the report supports those metrics.
• Check creative compatibility, size, loading behavior, and any relevant errors.
• Review page performance and ad-loading latency.

Google provides details on this issue in its guide to troubleshooting line-item delivery.

Reason 3: Video ads fail to play or register an impression

Video ad delivery has additional steps compared with a standard display placement. A video player may request an ad, receive a VAST response, attempt to load the creative, and then begin playback.

Not every request or response results in a counted video impression. For example, the player may encounter a VAST error, the creative may fail to load, or the user may navigate away before the applicable impression-counting event occurs.

How to investigate:

• Compare ad requests, code-served counts, and ad impressions using compatible video report metrics.
• Review VAST errors and video playback errors.
• Check whether the player is correctly handling the VAST response and playback events.
• Investigate timeouts, creative compatibility, and latency.
• Confirm that the reporting dimensions and metrics are appropriate for the video inventory.

Reason 4: Line items are not eligible to serve

A publisher may have many active line items in GAM, but an active line item does not necessarily qualify for every ad request. Its targeting, schedule, creative, inventory size, priority, and delivery settings determine where it can compete.

For example, a line item may target desktop traffic in one country, while the request comes from a mobile user in another country. The line item exists, but it is not eligible for that request.

How to investigate:

• Check the requested ad unit and size.
• Review targeting criteria and exclusions.
• Verify line-item dates, delivery settings, and creative association.
• Open the line item’s Troubleshoot tab to review available non-delivery causes.

Use the official line-item delivery troubleshooting guide to investigate the specific line item.

Reason 5: Reporting metrics use different definitions

Sometimes the apparent gap is caused by comparing metrics that do not measure the same stage of delivery. For example, a report may show total ad requests, while another shows impressions, filled requests, or a specialized video metric.

Even metrics with similar names can have different counting rules depending on the report type and inventory.

Before diagnosing a technical issue, verify:

• Both reports use the same date range and time zone.
• The metrics refer to the same inventory and demand scope.
• The dimensions and filters are comparable.
• The metrics are supported together in the selected report type.
• Reporting data has had sufficient time to update.

Consult the current Google Ad Manager interactive report metrics reference to confirm what each metric measures and which report types support it.

5. Example: 100,000 Ad Requests but 82,000 Impressions

Imagine a publisher’s report shows 100,000 ad requests and 82,000 impressions over a selected reporting period. The figures below are illustrative and do not represent a universal GAM ratio.

The numerical difference is 18,000, but it should not automatically be described as 18,000 unfilled impressions. Some of the difference may be associated with unfilled inventory, different metric definitions, rendering failures, or other delivery-stage differences.

To identify the actual cause, examine the relevant GAM metrics and diagnostic reports rather than assuming that subtracting impressions from requests identifies the exact failure category.

6. How to Troubleshoot the Difference in Google Ad Manager

Follow this workflow when ad requests are consistently higher than impressions or when the gap suddenly increases.

1. Confirm the reporting period. Select the same date range and time zone in every report you compare.
2. Verify the metrics. Confirm that you are comparing compatible request and impression definitions for the relevant inventory.
3. Break down the data. Review the difference by ad unit, requested size, device, geography, and date where those dimensions are available.
4. Check unfilled impressions. Find placements with elevated unfilled counts and investigate line-item eligibility and demand.
5. Review delivery troubleshooting. Use the line item’s Troubleshoot tab and relevant delivery tools to inspect non-delivery causes.
6. Check rendering and latency. If code-served counts are high relative to impressions, investigate whether creatives are loading and rendering successfully.
7. For video, inspect VAST and playback errors. Confirm that the player and creative complete the required delivery and impression-counting steps.
8. Compare the same segments over time. Determine whether the gap is normal for that inventory or a new change that requires attention.

7. How to Find Unfilled Impressions in GAM

Unfilled impressions are an important place to start when investigating requests that do not return ads.

1. Open Google Ad Manager and go to its reporting interface.
2. Create or open a report that supports the relevant inventory and metrics.
3. Select the date range you want to investigate.
4. Add the Ad unit and Requested ad sizes dimensions where available.
5. Add the Unfilled impressions metric.
6. Run the report and identify the ad units and sizes with the highest unfilled counts.
7. Use GAM delivery tools to investigate why no eligible line item returned an ad.

Google’s reporting interface has been transitioning to Interactive reports, so the exact navigation and metric availability may differ from older instructions. Use the current reporting interface and consult Google’s unfilled-impression troubleshooting documentation.

8. What Is a Healthy Difference Between Requests and Impressions?

There is no single request-to-impression ratio that is healthy for every publisher. The expected relationship depends on the inventory format, demand sources, page and player implementation, metric definitions, and how impressions are counted.

Instead of aiming for a universal percentage, establish a baseline for each important inventory segment and investigate significant changes.

Monitor the following together:

• Ad requests: The volume of opportunities sent to the ad-serving system.
• Unfilled impressions: Requests that did not return an ad under the relevant GAM metric definition.
• Code served and impressions: Delivery-stage metrics that can help reveal rendering or counting differences when available together.
• Creative render rate: The rate at which served line items successfully render a creative, as defined in GAM’s troubleshooting tools.
• Revenue and eCPM: The commercial impact of any delivery changes.

A larger gap is not necessarily a technical fault, but a sudden change is worth investigating. Compare like-for-like periods and check for recent changes to tags, creatives, inventory, demand, and reporting configuration.

9. Frequently Asked Questions

Official Google Ad Manager Resources

• Troubleshoot unfilled impressions in Ad Manager — causes and investigation steps for inventory that does not return an ad.
• Troubleshoot Ad Manager line-item delivery — recent changes, non-delivery causes, and creative render rate.
• Interactive report metrics reference — definitions and report availability for GAM metrics.