Integration

AppLovin Auction adapter for CloudX Android SDK. Supports App Open, Interstitial, Rewarded, and Native.

This page covers Android integration. Signed-in publishers can open the AppLovin Auction setup guide from the CloudX documentation dashboard.

The Android adapter supports App Open, Interstitial, Rewarded, and Native. Banner and MREC are not supported.

Install

The adapter is published to Maven Central. Make sure your project includes mavenCentral():

dependencyResolutionManagement {
    repositories {
        mavenCentral()
    }
}

Then add the adapter:

dependencies {
    implementation("io.cloudx:adapter-applovin:13.6.3.0")
}

dependencies {
    implementation 'io.cloudx:adapter-applovin:13.6.3.0'
}

The adapter includes the pinned AppLovin MAX SDK as a transitive dependency.

Initialization

Initialize CloudX with your CloudX app key as usual. CloudX receives the MAX SDK key and MAX ad-unit IDs from server configuration.

The adapter initializes MAX when AppLovin Auction placements are provisioned. If another component initializes MAX first, it must use the same SDK key.

The adapter is discovered automatically. No manual factory registration is required.

Privacy

Set consent through the CloudX privacy API before CloudX initialization when possible.

The adapter forwards explicit CloudX values to MAX:

• User consent maps to AppLovinPrivacySettings.setHasUserConsent.
• Do Not Sell maps to AppLovinPrivacySettings.setDoNotSell.

The adapter also forwards later explicit privacy updates.

Cached ads and revenue

The adapter keeps one eligible MAX fill for each provisioned placement. A loss retains it. A win consumes the exact fill and starts a replacement load.

MAX reports realized revenue through the displayed ad’s paid event. CloudX sends it with the AppLovin Auction impression and suppresses duplicate global AppLovin ILRD for that placement.

Compatibility

Support

For support, contact support@cloudx.io.