Delivery Inspector for desktop

The Delivery Inspector gives information on which ads were delivered. When unexpected ads deliver, use the Delivery Inspector to find out why. The details can help you answer:

  • Which ads delivered on my page.
  • Why these ads delivered and not others.
  • If line items and creatives are configured correctly.
  • Why line items are underdelivering, or not delivering at all.
  • Which line item would deliver if you were to request the ad slot again.

You simply enter the page’s URL to troubleshoot, and DFP provides the request and delivery details. You can also share the details with other users in your network.

Delivery Inspector (3:59)

Access Delivery Inspector for desktop

  1. From a computer, sign in to DoubleClick for Publishers.
  2. Click Delivery and then Troubleshoot.
  3. Remain on the default Web subtab.
  4. Enter the desktop page’s URL and click Troubleshoot.
  5. Your webpage appears in a new tab, with yellow overlays over the ads served by DFP that give you information about that ad slot.
    • You should also see the Google Publisher Console open at the bottom of the page. If there are lazy-loaded ads that require some user interaction to load, make sure you scroll through the page to ensure that these load.
    • The technical tagging information displayed at the bottom isn’t the Troubleshoot page.
  6. (Optional) On the webpage, if you click the ad you want to troubleshoot, its details will be automatically expanded when you return to the DFP Troubleshoot page.
  7. IMPORTANT: Navigate back to the DFP Troubleshoot page to see delivery details.
    You can share the details with another user in your network by clicking Share this session above the details.

Analyze the details

In the delivery details that appear on the Troubleshoot page:

  • Each row represents an ad slot and request.
  • Click a row to expand more details.
    • The “Div” field identifies where on the page the ad slot appears (such as “Top”). Each slot is tied to the page, but the “Div” is what distinguishes the slots.
    • Details also appear about what was requested (sizes, key values, etc.) and what was served (order, line item, creatives, etc.). Click the link next to each detail for more information.
    • You can click Simulate Request to help determine why a different ad delivered than the one you expected.
From your webpage that appeared in a new window or tab in the steps above, if you click one of the ad slots overlayed in yellow, the related entry will be selected and expanded on the DFP Troubleshoot page.

Share the 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 coppied 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

The Simulate request feature 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. You can then change targeting and tag information to try and get the desired line item to win the simulation.

When you click Simulate request as mentioned above, the following sections appear.

The Simulate request feature doesn’t retain information on page or server state. Therefore, competitive exclusions, roadblocks, and frequency caps won’t match the original request.

“Original request” section

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” section

This section shows what would happen if you were to request this ad slot again. It includes:

  • Ad request details: The request and targeting information for the simulated request. It defaults to the current settings.
  • Winning line item details: 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 DFP 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 article helpful?
How can we improve it?