> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudx.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Vungle
> Use this guide to configure Vungle bidding in CloudX.
Keep using the platform integration guides for SDK installation and ad loading:
* [Android integration guide](/en/android/integration)
* [iOS integration guide](/en/ios/integration)
For iOS-specific Vungle adapter requirements, see the [Vungle Adapter page](/en/ios/adapters/vungle/overview).
## Overview
Use the following values:
* `Vungle App ID` in CloudX app mapping
* `Vungle Placement ID` in CloudX ad-unit mapping
* CloudX `app_key` and CloudX ad unit identifiers in app code
CloudX uses the bidder name `Vungle` in the dashboard. If you see Liftoff branding in external network materials, it refers to the same network here.
CloudX collects Vungle bidder tokens internally, so you do not need to fetch Vungle bidder tokens in your app code.
## Step 1. Complete Vungle-side setup
1. Sign in to your Vungle or Liftoff Monetize publisher account.
2. Add the app you want to monetize.
3. Copy the Vungle App ID for that app.
4. Create placements for each format you want to use.
5. Copy each placement ID.
6. Complete Vungle review and payout setup before expecting live demand.
## Step 2. Enable Vungle in CloudX
Go to `Operations -> Bidder Configuration` and make sure `Vungle` is enabled for your account.
If Vungle is disabled, CloudX will not request bids even if your mappings are correct.
## Step 3. Configure your CloudX app
Go to `Inventory -> Apps` and create or open the app that matches your mobile application.
| CloudX field | Value to enter | Required |
| --------------- | ------------------ | -------- |
| `Vungle App ID` | Your Vungle App ID | Yes |
Also copy the CloudX `app_key` from the app details page. Use the CloudX `app_key` in Android or iOS code.
## Step 4. Configure CloudX ad units
Go to `Inventory -> Ad units` and add the mapping below for each eligible ad unit.
| CloudX field | Value to enter | Required |
| --------------------- | --------------------------------------------------- | -------- |
| `Vungle Placement ID` | The Vungle placement ID for that ad unit and format | Yes |
* Treat `Vungle Placement ID` as required on both platforms.
* Match the placement to the correct CloudX ad-unit format.
* Use a separate placement for each CloudX ad unit or format as needed.
## Step 5. Add Vungle line items
Create line items for bidder `Vungle` on each CloudX ad unit where Vungle should compete.
* Use bidder `Vungle`
* Match the line item to the correct ad format
* Repeat the setup for each ad unit where Vungle should bid
## Step 6. Finish app integration
Use the CloudX platform guides and the iOS Vungle adapter page:
* [Android integration guide](/en/android/integration)
* [iOS integration guide](/en/ios/integration)
* [Vungle Adapter page](/en/ios/adapters/vungle/overview)
In app code:
* Initialize CloudX with the CloudX `app_key`
* Load ads using CloudX ad unit identifiers
* Do not pass Vungle App IDs or Placement IDs into app code
* For Interstitial and Rewarded ads, call `show()` only after the ad is ready
## Step 7. Test and validate
1. Enable test mode for your device in CloudX.
2. Build and run the app with the CloudX `app_key` and the correct CloudX ad unit identifiers.
3. Request an ad from each mapped ad unit.
4. Confirm that the ad loads and that Vungle participates or wins where expected.
## Troubleshooting
### Vungle is not bidding
Check the following first:
* `Vungle` is enabled in `Operations -> Bidder Configuration`
* The app has a valid `Vungle App ID`
* The ad unit has a valid `Vungle Placement ID`
* A `Vungle` line item exists for the ad unit
### Vungle bids but the ad does not render
Check the following:
* Your app is using the CloudX `app_key`, not a Vungle ID
* Your app is loading the intended CloudX ad unit
* The placement belongs to the correct Vungle app and format
* On iOS, the requirements from the [Vungle Adapter page](/en/ios/adapters/vungle/overview) are complete
### The placement looks correct but loads still fail
The mobile adapters require a valid `Vungle Placement ID` at load time. Re-check the ad-unit-level placement mapping in CloudX.
## Mapping Reference
| CloudX field | Internal key | Scope |
| --------------------- | -------------- | ------- |
| `Vungle App ID` | `app_id` | App |
| `Vungle Placement ID` | `placement_id` | Ad unit |