InMobi
Use this guide to configure InMobi bidding in CloudX.
Keep using the platform integration guides for SDK installation and ad loading:
For platform-specific InMobi adapter requirements, see:
Overview
Use the following values:
InMobi Account IDinOperations -> Bidder Configuration- InMobi placement IDs on CloudX ad units
- CloudX
app_keyand CloudX ad unit identifiers in app code
InMobi is different from Meta, Mintegral, and Vungle because the main InMobi account credential is configured at the bidder or account level in CloudX, not as a per-app SDK key.
CloudX collects InMobi bidder tokens internally, so you do not need to fetch InMobi bidder tokens in your app code.
Step 1. Complete InMobi-side setup
- Sign in to your InMobi publisher account.
- Copy your InMobi Account ID.
- Create placements for each format you want to use.
- Copy each placement ID.
- Complete InMobi review and payout setup before expecting live demand.
Step 2. Enable InMobi in CloudX and add the account ID
Go to Operations -> Bidder Configuration and make sure InMobi is enabled for your account.

Enter your InMobi Account ID there. CloudX uses this account-level value when initializing the InMobi SDK.

Step 3. Configure CloudX ad units
Go to Inventory -> Ad units and add the InMobi placement mapping for each eligible ad unit.

| CloudX field | Value to enter | Required |
|---|---|---|
InMobi placement ID | The numeric InMobi placement ID for that ad unit and format | Yes |
- Use the numeric placement ID from InMobi.
- Match the placement to the correct CloudX ad-unit format.
- No separate app-level InMobi mapping is required for the standard CloudX setup.
Step 4. Add InMobi line items
Create line items for bidder InMobi on each CloudX ad unit where InMobi should compete.

- Use bidder
InMobi - Match the line item to the correct ad format
- Repeat the setup for each ad unit where InMobi should bid
Step 5. Finish app integration
Complete the integration and adapter setup for your platform:
- Android integration guide
- iOS integration guide
- Unity integration guide
- Android InMobi Adapter page
- iOS InMobi Adapter page
- Unity InMobi Adapter page
In app code:
- Initialize CloudX with the CloudX
app_key - Load ads using CloudX ad unit identifiers
- Do not pass InMobi Account IDs or placement IDs into app code
- For Interstitial and Rewarded ads, call
show()only after the ad is ready
Step 6. Test and validate
- Enable test mode for your device in CloudX.
- Build and run the app with the CloudX
app_keyand the correct CloudX ad unit identifiers. - Request an ad from each mapped ad unit.
- Confirm that the ad loads and that InMobi participates or wins where expected.
Troubleshooting
InMobi is not bidding
Check the following first:
InMobiis enabled inOperations -> Bidder ConfigurationInMobi Account IDis configured in bidder settings- The ad unit has a valid numeric InMobi placement ID
- An
InMobiline item exists for the ad unit
InMobi bids but the ad does not render
Check the following:
- Your app is using the CloudX
app_key, not an InMobi account credential - Your app is loading the intended CloudX ad unit
- The placement ID is numeric and belongs to the correct InMobi format
- On iOS, the requirements from the InMobi Adapter page are complete
The placement looks correct but loads still fail
The mobile adapters expect a valid numeric placement_id. Re-check the ad-unit-level placement mapping in CloudX and make sure the value was copied without formatting changes.
Mapping Reference
| CloudX field | Internal key | Scope |
|---|---|---|
InMobi Account ID | account_id | Bidder/account |
InMobi placement ID | placement_id | Ad unit |