Dr. Prebid is a validation and troubleshooting app for publishers implementing Prebid Mobile. With this app you can validate your settings for your ad server setup, your Prebid Server configuration, and your end-to-end Prebid Mobile SDK implementation.
This app is available for iOS and Android:
Download for iOS
System Requirements: Requires iOS 12.0 or later. Compatible with iPhone, iPad, and iPod touch.
Download for Android
System Requirements: Requires Android 4.2 and up.
Dr. Prebid is an open source app. You can find the source on the Prebid GitHub site:
Review the Prebid.org Dr. Prebid Terms of Use.
Enter your test values on the Dr. Prebid Setup screen.
Dr. Prebid Setup Screen
The following are descriptions of the fields available in Dr. Prebid. Tap on a field to change its value. All fields are required.
In this section, define the ad format and size of the ad server ad unit you’ll be testing.
Ad Format
The type of ad you want to test. This will be the ad type that is associated with the line item you’re testing against in your ad server setup.
Select from:
Ad Size
The size of the ad for the ad slot you’ll be filling. This field applies only to the Banner ad format.
These settings will enable you to test whether the Prebid Mobile line item in your ad server is set up correctly.
Ad Server
The primary ad server you’re using to serve your ads.
Select from:
Bid Price
The decimal value (in USD) of the bid price bucket your line item is targeting. For example, if you have a line item targeting hb_pb:0.50, enter 0.50 in the Bid Price field to test whether this line item can serve.
Note that Dr. Prebid will not round this value using price buckets, so be sure that you have a line item targeting this bid price.
Ad Unit ID
The unique, user-defined identifier for the relevant ad slot in the primary ad server. You can find this value in the ad unit ID field of your Prebid Mobile implementation.
You can manually type in your ad unit ID or you can copy/paste via the Scan QR code option. (See “QR Code Scanning” below for instructions.)
These settings will help verify that Prebid Mobile and Prebid Server are connected, and that your demand partners are returning bid responses.
Server Host
Select your Prebid Server host:
Custom Server Host Provide the url of the custom hosted prebid server
Account ID
Your Prebid Server account ID. This is the account ID you were assigned when you registered with your Prebid Server host.
You can manually type in your account ID or you can copy/paste via the Scan QR code option. (See “QR Code Scanning” below for instructions.)
Config ID
Your Prebid Server configuration ID for the ad unit. This is the ID of the server-side configuration you defined in Prebid Server for the ad unit you’re testing.
You can manually type in your account ID or you can copy/paste via the Scan QR code option. (See “QR Code Scanning” below for instructions.)
IDs for ad units and Prebid Server accounts and configurations are long strings that can be tedious to type manually and are prone to typing errors. To avoid manually entering an ID, you can perform what results in a copy-and-paste action by creating and scanning QR codes for the IDs.
To set up a QR code, follow these steps:
Go to any QR code generator. (There are many free options for QR code generation. Examples include https://www.qr-code-generator.com/ and https://www.the-qrcode-generator.com/.)
Copy the ID you want to use from your Ad Server or from Prebid Server, depending on which ID you’re working with.
In the QR code generator, select the Text option, paste in the ID, and generate the code.
In Dr. Prebid, tap Scan QR code for the appropriate ID. This will open your QR code scanner (your camera).
Scan the code. The ID will now be in the ID field in Dr. Prebid.
IMPORTANT: Make sure you copy the full ID into the QR code generator. Also check to make sure you don’t copy in any extra trailing spaces. These will cause your validation tests to fail.
After you’ve entered all the values on the Setup screen, tap Run Tests to begin your validation.
Validation Test Summary Screen
Three validation tests are performed: Ad Server Setup, Real-Time Demand, and End-to-End SDK Configuration. Each test will be displayed with either a green check mark (passed) or a red X (failed).
Passed | Failed | |
---|---|---|
The steps performed within each validation will also be displayed, each signifying whether that step passed or failed.
Tap the step within a validation test for details on the pass or failure results.
This test determines whether your Prebid Mobile line items are configured correctly in your primary ad server.
The test generates Prebid-specific key-value pairs representing the bid price you specified in the Bid Price field of your setup. Based on the Ad Format you selected, these key-values are set on the banner ad views or interstitials, and a test ad is loaded to determine whether any matching Prebid line items will be selected.
Results
Success: If the test is successful, all steps will display green check marks. Tap into the Prebid Mobile creative HTML served screen to compare the ad server creative to the Prebid.org test creative. The Received Creative and the Expected Creative should be identical.
Failure: If the test fails, either no Received Creative will appear, or the Received Creative will not match the Expected Creative. In either case, check the following:
hb_pb
value with an active creative of the appropriate size and format.This test validates that the real-time requests generated using your Prebid Server Account ID and Prebid Server Configuration ID are reliably returning demand. If the account ID and configuration ID that you entered are successfully resolved on Prebid Server, Dr. Prebid will initiate a test in which 100 bid requests are sent to the demand partners included in your configuration. In a successful test these auctions will produce valid bid responses.
A summary of results will be displayed:
Bid Response Summary
Tap n bid responses received to see a breakdown of bid responses by demand partner. For each demand partner you’ll see the following details:
On the Bid Response Summary screen, tap Request & Response for a demand partner to see the bid request sent to the demand partner and a response received (if any).
Results
There are three possible outcomes from this validation test:
Success: The auctions ran successfully and at least one valid bid response was returned from any one of the demand partners. A bid response will be returned in the results for each bidder.
Failure: The auctions ran successfully, but no successful bid responses were returned.
Failure: No auctions were run. If no auctions were run, verify the following in your setup:
This test is a full end-to-end validation in which the Prebid Mobile SDK communicates with Prebid Server (using your account and configuration details) and with the primary ad server SDK.
The summary screen displays the following information:
Results
Possible outcomes from this test:
Success: This is a full, end-to-end validation of your Prebid Mobile implementation using your Prebid Server account ID and configuration ID. The validation succeeds if every step passes.
Failure: There are many steps throughout this validation. If a problem is encountered at any step, the validation will be marked as failed. Some general things to check if this test fails include:
hb_cache_id
with an alphanumeric GUID.)Here are some more specific things to look for and actions to take based on which step(s) of the validation failed.
hb_cache_id
with an alphanumeric GUID.