Inspect mobile app ad delivery

Inspect ads that appear on your mobile app

See which ads are eligible to deliver to your mobile app content to better understand the DoubleClick for Publishers (DFP) ad selection process or troubleshoot issues related to delivery. Simply link a device to see ad request and delivery details. You can then share the details with other users in your network.

Watch related Publisher University training

Below are some common questions answered by DFP delivery tools:

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

Get started

Before inspecting delivery in your mobile app, you need to link your mobile device to DFP to initiate inspection. Then, open DFP to see delivery details from your linked mobile app.

Initiate inspection in your mobile app

  1. On your mobile device, open your mobile app and find an ad served by your DFP network.
  2. Swipe right, left, right, left and then release your finger. Watch a video of this gesture

    Be careful to not repeatedly tap the creative as accidental clicks might be mistaken for spam.

    What if the debug gesture doesn't work for my creative?
    Some creatives, such as custom native ads, aren't compatible with the debug gesture. As an alternative, you can add a special function in your mobile app's code to trigger the in-app menu. For example, you might add this function to a special button or gesture.  iOS | Android
  3. Tap Troubleshooting in the debug menu.

    If this is your first time inspecting delivery this mobile app on your mobile device, you'll need to sign in to DFP to confirm that you're an active user in the network and authorized to see delivery information. Sign in using your DFP username and password and choose a name for your device so you can identify it in DFP.

Open DFP to collect ad delivery details

  1. On your computer, sign in to DoubleClick for Publishers.

    Make sure you're signed in to the same DFP account and network as your device.

  2. Click Delivery and then Troubleshoot and then Mobile app.
  3. Under "Linked devices," select the device you just linked in your most recent session.

Reload the ads on your mobile app

Now that you've linked your device to initiate inspection and opened DFP, you're ready to start collecting ad delivery details. Details for any ads loaded before completing the steps above will not appear in DFP.

  1. On your mobile device, reload the mobile app page, or start using the app.
  2. As ads load in your mobile app, information about delivery will appear in DFP.

Inspect delivery details 

In DFP 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 "Exchange Bidding" or "Ad server". Learn more
  • Advertiser, Order, line item, creative name and ID. Click the ID to open it in DFP.
  • Line item type
  • Creative size
  • Creative type

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 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.

Allow others to access your devices (optional)

Linked devices are private by default, meaning that only you can use them in DFP. If you want to open up the device for others to use for troubleshooting, you can update the settings in the DFP Admin section.

  1. In DFP, Click Admin and then Access & authorization and then Linked devices.
  2. In the “Visibility” column, click a cell, and select Public from the dropdown.
Was this article helpful?
How can we improve it?