Delivery Inspector for apps
Delivery Inspector for apps 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 app.
- 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.
To troubleshoot delivery for apps, you first trigger the in-app pop-up menu on your mobile device, link the device if needed, and then use DFP to activate the troubleshooting details. You can then share the details with other users in your network.
- On your mobile device, open your app and perform a debug swipe on any creative as follows:
If your creatives don’t allow a debug swipe (custom native ads for example), an alternative linking option is provided via a code function in iOS. You can add this function anywhere in the code where you’d like to trigger the in-app menu (to a button, a gesture, etc.). Refer to the “Prepare your app” section in the developer docs for iOS and Android for instructions.
- Press and hold a finger on the creative.
- Swipe right, left, right, left and then release your finger.
- Be careful to not accidentally repeatedly press the creative as it could result in accidental clicks that Google may flag as ad spam.
- If you’ve used Troubleshooting tools in the past on this device, then you’re automatically linked.
If you haven’t yet used Troubleshooting tools, the “Debug options” menu will appear. You’ll need to link the device to a DFP account:
- On the menu, click Troubleshooting.
A browser opens to the DFP sign-in page.
- Sign in using your DFP username and password.
- Under “Verify device link,” name your device for future use in the DFP UI (e.g., “DoubleClick Device #1”) and click Verify.
- On the menu, click Troubleshooting.
Once you have a device linked, you can use DFP on your computer to start the Troubleshooting tool.
- 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.
- Click Delivery Troubleshoot.
- Click the Mobile app subtab.
- Select the device you just linked in your most recent session.
- Go back to your mobile device, trigger the “Debug Options” menu again, and click Troubleshoot.
This allows the SDK to verify that the device linking was successful and to enable troubleshooting.
- If the device linking was successful, the “Debug Options” menu will close immediately.
- If it was unsuccessful, you’ll be prompted to link your device again.
- Load an ad for the slot you want to troubleshoot.
- Back on your computer, the Troubleshoot page shows the delivery details for that ad.
You can share the details with another user in your network by clicking Share this session above 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 app the ad slot appears (such as “Top”). Each slot is tied to the app, 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.
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.
- Above the details that appear on the Troubleshoot page, click Share this session.
- From the pop-up that appears, click Copy URL.
The URL is now coppied to your clipboard and ready to be pasted
- Send the URL to a user with access to your network.
Tell the user to paste the URL into their browser.
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.
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.
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.
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.
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.
- In DFP, Click Admin Access & authorization Linked devices.
- In the “Visibility” column, click a cell, and select Public from the dropdown.