Integration
AdMob/GAM estimated adapter for CloudX Android SDK. Serves AdMob waterfall demand on either the Google Mobile Ads SDK or the GMA Next-Gen SDK, and Google Ad Manager demand on the Google Mobile Ads SDK, for Banner, MREC, Interstitial, Rewarded, Native, and App Open placements.
For dashboard configuration, see the AdMob/GAM estimated publisher setup guide.
Pricing and the Google-side eCPM floor are dashboard and console decisions, not app-side ones. See the “Pricing: automatic or manual” and “Set an eCPM floor: Google Optimized or Manual” sections of the AdMob/GAM estimated publisher setup guide.
The Google adapter serves both AdMob estimated and Google Ad Manager estimated demand — AdMob waterfall and Google Ad Manager, respectively. On Android there are two adapter artifacts, one for each generation of Google’s ad SDK. Pick the one that matches the Google SDK your app integrates.
Which Google demand you get
The adapter serves two independent Google demand sources:
- AdMob estimated — AdMob waterfall demand.
- Google Ad Manager estimated — Google Ad Manager demand.
Which one runs is a dashboard decision, not a code one. You enable the ad source per placement in the CloudX dashboard; there is no extra dependency and no app-side change. Both sources may run in the same app, each with its own mapping and CPM target, and both may bid in the same auction. Which artifact you integrate does constrain Ad Manager demand — see below.
Google Ad Manager demand is supported from adapter-googlewaterfall 25.2.0.2. Ad Manager placements are served through the same Google Mobile Ads SDK you already integrate, so no extra dependency is required. CloudX selects them per placement from your server-side configuration — there is nothing to enable in your app. adapter-admob does not serve Ad Manager demand and skips those placements.
Which SDK are you on?
You must integrate exactly one of the two artifacts below. The two Google SDK generations ship colliding classes and cannot coexist in a single app.
- Google Mobile Ads SDK (
play-services-ads25.x) — the standard AdMob SDK. Useio.cloudx:adapter-googlewaterfall. - GMA Next-Gen SDK (
com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk1.3.0) — Google’s Kotlin-first replacement. Useio.cloudx:adapter-admob.
Both artifacts have full format parity: Banner, MREC, Interstitial, Rewarded, App Open, and Native. Dashboard mapping, placements provisioning, and revenue semantics are identical.
Ad Manager ad unit ids take the form /NNNNNNN/placement/name, unlike AdMob’s plain ad unit id.
Install
Use this track if your app integrates the Google Mobile Ads SDK (play-services-ads 25.x).
dependencies {
implementation("io.cloudx:adapter-googlewaterfall:25.2.0.5")
}dependencies {
implementation 'io.cloudx:adapter-googlewaterfall:25.2.0.5'
}Use this track if your app integrates the GMA Next-Gen SDK (ads-mobile-sdk 1.3.0).
dependencies {
implementation("io.cloudx:adapter-admob:1.3.0.4")
}dependencies {
implementation 'io.cloudx:adapter-admob:1.3.0.4'
}Android Manifest
Publisher setup is the same for both tracks. The Google SDK requires an AdMob app ID in your application’s manifest:
<application>
<meta-data
android:name="com.google.android.gms.ads.APPLICATION_ID"
android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy" />
</application>If this metadata is missing, the adapter fails initialization before Google SDK init runs. Apps that only use Google Ad Manager may declare the boolean com.google.android.gms.ads.AD_MANAGER_APP meta-data instead of an app ID.
Impression-Level Revenue Data
Impression-Level Ad Revenue must be on for the AdMob account, or CloudX records no revenue for Google impressions and automatic pricing never learns a realized price. See the “Turn on Impression-Level Ad Revenue” section of the AdMob/GAM estimated publisher setup guide. Google Ad Manager estimated demand reports impression-level revenue through your Ad Manager setup instead.
Compatibility
Google Mobile Ads SDK — adapter-googlewaterfall
| Adapter version | Network SDK | Minimum CloudX SDK |
|---|---|---|
25.2.0.5 | Google Mobile Ads SDK 25.2.0 | 4.5.0 |
25.2.0.4 | Google Mobile Ads SDK 25.2.0 | 4.5.0 |
25.2.0.3 | Google Mobile Ads SDK 25.2.0 | 4.5.0 |
25.2.0.2 | Google Mobile Ads SDK 25.2.0 | 4.5.0 |
25.2.0.1 | Google Mobile Ads SDK 25.2.0 | 4.2.0 |
25.2.0.0 | Google Mobile Ads SDK 25.2.0 | 4.2.0 |
25.1.0.6 | Google Mobile Ads SDK 25.1.0 | 4.5.0 |
25.1.0.5 | Google Mobile Ads SDK 25.1.0 | 4.5.0 |
25.1.0.4 | Google Mobile Ads SDK 25.1.0 | 4.2.0 |
25.1.0.3 | Google Mobile Ads SDK 25.1.0 | 4.2.0 |
25.1.0.2 | Google Mobile Ads SDK 25.1.0 | 4.2.0 |
25.1.0.1 | Google Mobile Ads SDK 25.1.0 | 4.1.0 |
25.1.0.0 | Google Mobile Ads SDK 25.1.0 | 4.1.0 |
24.9.0.1 | Google Mobile Ads SDK 24.9.0 | 4.5.0 |
24.9.0.0 | Google Mobile Ads SDK 24.9.0 | 4.2.0 |
23.6.0.0 | Google Mobile Ads SDK 23.6.0 | 4.1.0 |
Next-Gen SDK — adapter-admob
| Adapter version | Network SDK | Minimum CloudX SDK |
|---|---|---|
1.3.0.4 | GMA Next-Gen SDK 1.3.0 | 4.5.0 |
1.3.0.3 | GMA Next-Gen SDK 1.3.0 | 4.5.0 |
1.3.0.2 | GMA Next-Gen SDK 1.3.0 | 4.5.0 |
1.3.0.1 | GMA Next-Gen SDK 1.3.0 | 4.5.0 |
1.3.0.0 | GMA Next-Gen SDK 1.3.0 | 4.2.0 |
Requires minSdk 24.
The adapter is discovered automatically when your server-provisioned CloudX configuration includes AdMob estimated or Google Ad Manager estimated demand. No manual adapter registration is required.