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.

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-ads 25.x) — the standard AdMob SDK. Use io.cloudx:adapter-googlewaterfall.
• GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk 1.3.0) — Google’s Kotlin-first replacement. Use io.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

dependencies {
    implementation("io.cloudx:adapter-googlewaterfall:25.2.0.1")
}

dependencies {
    implementation 'io.cloudx:adapter-googlewaterfall:25.2.0.1'
}

dependencies {
    implementation("io.cloudx:adapter-admob:1.3.0.0")
}

dependencies {
    implementation 'io.cloudx:adapter-admob:1.3.0.0'
}

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.

Impression-Level Revenue Data

Enable AdMob impression-level revenue data in the AdMob console so served impressions and paid values can be reported through CloudX:

AdMob console -> Account -> Account info -> Impression-level ad revenue.

That console setting covers AdMob estimated demand. Google Ad Manager estimated demand reports impression-level revenue through your Ad Manager setup instead.

Compatibility

Google Mobile Ads SDK — adapter-googlewaterfall

Next-Gen SDK — adapter-admob

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.