This app allows DSP Partners on the InMobi Exchange to observe, troubleshoot, and analyze how their ads render on publishers using the InMobi SDK by pasting a custom OpenRTB bid response and instantly previewing the result across supported placement types, without needing a live campaign.
Support for the Native placement type and Native ad format will be built in subsequent versions.
Contact your InMobi Account Manager to get a Partner Key (a unique alphanumeric key issued per DSP) before logging in.
If you're accessing the app from China, connect to a VPN service first.
After logging in, you'll land on the home screen. Under Select Placement, select the placement type you want to test: Rewarded, Interstitial, MREC, or Banner.
Tap the share icon (top-right) to export your bid response and activity log as a JSON file, which you can send to your InMobi contact or share internally with your team for troubleshooting.
Reach out to your InMobi Account Manager. Each Partner Key is a unique alphanumeric string mapped to your DSP account.
Yes, a single Partner Key can be used on multiple devices at the same time, up to InMobi's configured device limit.
Interstitial, Rewarded, MREC (300x250), and Banner (320x50). Native support is coming soon.
A standard OpenRTB-compliant bid response JSON, with a valid ADM (ad markup) field for the placement type you're testing.
Use the Clear button next to the Bid Response field. You'll be asked to confirm before it's cleared.
Tap the share icon in the top-right corner of the placement screen to export your bid response and Activity log as a JSON file.
Open the app's About/More section on the home screen. It displays both the App Version and the SDK Version.
Reach out to your InMobi Account Manager or Solutions contact with a description of the issue and, if possible, the shared JSON file from the app.
| Error Message | Description | Resolution |
|---|---|---|
| Invalid Key. Kindly retry with the correct key. | DSP Partner key is wrong. | Contact your InMobi Account Manager for a valid key. |
| Something went wrong | InMobi server connectivity issue | Wait a moment and retry. If it persists, contact your InMobi contact. |
| Error Message | Description | Resolution |
|---|---|---|
| Invalid JSON or Unable to prepare bid response payload |
The used content isn’t valid JSON. | Double-check the JSON structure (matching braces/brackets, no trailing commas) and retry. |
| Invalid Bid Response: missing seatbid | The JSON is valid but is missing the required seatbid field. | Add a valid seatbid object to the response and retry. |
| Invalid Bid Response: missing bid | The bid response is missing the bid object. | Add a valid bid object inside seatbid and retry. |
| Invalid ADM | The bid is missing the ADM (ad markup) field. | Include a valid ADM field in the bid object and retry. |
| Invalid Bid Response (unsupported ADM format) | The bid response has an unsupported ad type | Use a supported ADM format (VAST/String) for the placement type. |
| The SDK encountered an internal error or Server returned a no-fill. Please try again. |
Ad rendering-related issue. | Export the log (Step 6) and share it with your InMobi contact. |
| The Internet is unreachable. Please check your Internet connection. | VPN/network-related issue on the device. | Check your device’s connection and retry. |
| Please provide a valid placement ID | The placement ID used is invalid. | Export the log (Step 6) and share it with your InMobi contact. |
| The Ad Server encountered an error when processing the ad request. This may be a transient issue. Please try again in a few minutes. | Server-side issue, usually transient. | Wait a few minutes and retry. |
| The Ad Request timed out waiting for a response from the network. This can be caused due to a bad network connection. Please try again after a few minutes. | Timeout fetching the ad response from the server. | Check your network connection and retry after a few minutes. |
| Unexpected Behaviors | Description | Resolution |
|---|---|---|
| Creative rejected: Ad doesn’t render and no error shown. | The creative was rejected during review on InMobi’s or the publisher’s end. | Check the creative’s review/approval status with your Account Manager. |
| Campaign paused: Ad doesn’t render and no error shown. | The creative or campaign was already paused on the partner’s end. | Confirm the campaign/creative is active on your end before testing. |
| “Show” button is grayed out. | Show activates only once the load completes successfully. | Check the Activity log for the failed stage and resolve that error first. |
| App is unreachable from Mainland China | Regional network restrictions block direct access. | Connect to a VPN service before opening the app. |
The exact wording may differ slightly on Android for some of these messages.
By installing this SDK update, you agree that your Children Privacy Compliance setting remains accurate or that you will update that setting, whenever there is a change in your app's audience. You may update the app's Children Privacy Compliance settings at https://publisher.inmobi.com/my-inventory/app-and-placements.
Support Center
