Inspect webpage ad delivery

Ad Manager delivery tools help you troubleshoot ads

The Webpage ads inspector is used to see which ads are eligible to deliver to your content. Inspecting eligible ads can help you troubleshoot or understand ad selection. You can inspect ads that appear in browsers that are used on desktops, laptops, on mobile devices (also referred as mobile web). The Webpage ads inspector can't be used to for ads that appear in mobile apps.

Some common questions that can be answered by the Webpage ads inspector are:

  • Which ads delivered on my page?
  • Why these ads and not others?
  • Are my line items and creatives set up correctly?
  • Why is my line item behind schedule or not delivering at all?

Details can be shared with other users in your network to help collaborate and troubleshoot.

Get started

You can inspect webpage ads in one of two ways for ads that show on desktop or laptop browsers. In Ad Manager, navigate to:

Delivery and then Delivery tools and then Webpage ads

Alternatively, use the Google Publisher Console. For mobile web, you can only start in Ad Manager.

Start in your webpage

  1. Open the webpage in a desktop or laptop browser.
  2. Open the Google Publisher Console.
  3. Click Troubleshoot.

Start in Ad Manager delivery tools

  1. Sign in to Google Ad Manager.
  2. Click Delivery and then Delivery tools.
  3. Click Webpage ads to inspect desktop or laptop browser delivery, or click Mobile web ads to inspect mobile browser delivery.
  4. Follow the on-screen instructions to open the page you want to inspect, then come back to Ad Manager to see delivery details.

Inspect delivery details

Make sure you switch back to Ad Manager to see ad details

The information displayed in the Google Publisher Console at the bottom of your webpage is not Ad Manager delivery tools. Switch back to your Ad Manager tab to see the details for each ad delivered in Ad Manager.

In Ad Manager delivery tools, information about each request and what ad delivered is displayed. Each row on the page represents an ad slot and request. Click a row to expand more details, then click Simulate Request to determine why a different ad delivered than the one you expected.

Information about requests

  • Div: Identifies where on the page the ad slot appears, such as "top".
  • Requested sizes: All sizes defined in the ad request.
  • Key values: All key-values defined in the ad request. Click see all to see the full list.

Information about what delivered

  • Demand channel: The method used to select the ad, such as "Open Bidding" or "Ad server". Learn more
  • Advertiser, order, line item, and creative, each with their associated IDs. To open each in Ad Manager, click their respective names .
  • Line item type
  • Creative size
  • Creative type

Block an Ad Exchange/AdSense ad or report an issue

The Creative details tab appears only if you're enabled for the "Review and block Ad Exchange creatives" user role permission.

Block Ad Exchange or AdSense creatives, or report a potential issue with them, via the Creative details tab. Next to "Suggestion", you can:

  • Block ad: Prevent the creative from serving. The blocked ads appears in the "Blocked" tab of Creative review.
  • Report to policy: Submit a creative that may have policy issues for review. 

These options are available only for Ad Exchange or AdSense creatives, not other kinds.

Share details

You can share the details with users who have access to your network. This allows you to easily collaborate with others to help determine a plan for troubleshooting your line items.

  1. Above the details that appear on the Troubleshoot page, click Share this session.
  2. From the pop-up that appears, click Copy URL.
    The URL is now copied to your clipboard and ready to be pasted
  3. Send the URL to a user with access to your network.
    Tell the user to paste the URL into their browser.

Simulate ad requests

Shows which line item would win if you were to request the ad slot again. If an unexpected line item wins the simulation, you can see why. Change targeting and tag information to try and get the desired line item to win the simulation.

When you click Simulate request , Ad Manager runs a simulation and provides the details outlined below. 

The "Simulate request" feature doesn’t retain information on page or server state. Competitive exclusions, roadblocks, and frequency caps will, therefore not match the original request.

Original request

This section recreates how the ad request you selected on the Troubleshoot page actually delivered. It includes:

  • Ad request details: The request and targeting information for the winning line item.
  • Winning line item details: The delivery details for the winning line item.
  • View non-delivery reasons: Click this button to see reasons why other line items were selected to serve over this one in cases that this line item was eligible. Here are details of the possible non-delivery reasons.

Simulation

Shows what would happen if you were to request this ad slot again. 

Ad request details

The request and targeting information for the simulated request. It defaults to the current settings.

Winning line item 

The delivery details for the line item that wins the simulation.

Search for the line item you were expecting to win

If an unexpected line item wins the simulation, you can use this box to search for the line item you thought would win and click Go. You’ll see a pop-up with the details for the winning line item on the left side, and the reasons for non-delivery of the line item you searched for on the right side. Here are details of the possible non-delivery reasons.

Rerun simulation

You can change the targeting and tag information under "Ad request details" and then click Rerun simulation to see if the winning line item changes. If you eventually find a simulation that provides the desired winning line item, you can go back and update the actual targeting and tag information.

Why is the line item that won the simulation different from the original winner?

There are several possible reasons for this. Here are a few:

  • Every run request, whether actual or simulated, happens dynamically. As a result, several things can change from one request to the other, including run time, goals, new line items to compete against, etc.
  • The ad selection process can result in different line items serving from one ad request to the next.
  • The simulation only considers one ad slot at a time. Therefore, if original winning line item is part of a request with multiple ad slots, like a roadblock, it won’t win the simulation.
  • The line item reached a frequency cap.
  • The line item met its delivery goal.
Was this helpful?
How can we improve it?