← ClaudeAtlas

admob-android-integrationlisted

Use when integrating AdMob on Android (legacy play-services-ads or the GMA Next-Gen SDK), migrating from another ad SDK (Appodeal, AppLovin MAX, ironSource, etc.) to AdMob, auditing an AdMob implementation against Google's official guidelines, or troubleshooting crashes/show rate/revenue problems in existing ad code
vmobifystudio/claude-admob-android-skill · ★ 0 · AI & Automation · score 72
Install: claude install-skill vmobifystudio/claude-admob-android-skill
# AdMob Android Integration ## Overview End-to-end reference for shipping a production-grade AdMob implementation on Android, audited against Google's six official guides (banner, interstitial, rewarded, app open, native, optimize-initialization). **Two SDKs exist. Decide which one the app uses before applying anything below.** Dependency `com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk` = Next-Gen → start with the **GMA Next-Gen SDK** section, which overrides the legacy patterns wherever they differ. Dependency `com.google.android.gms:play-services-ads` = legacy → the rest of this file applies. Covers: current SDK versions, Gradle setup, manifest wiring, UMP consent integration, Meta Audience Network mediation, all 5 ad formats with correct lifecycle, frequency capping, crash prevention, native ad layouts, migration from Appodeal, and a 22-point audit checklist. ## When to use - Starting fresh AdMob integration on an Android app - Migrating from Appodeal / AppLovin MAX / ironSource / any other ad SDK - Auditing existing ad code for crashes, memory leaks, or low show rate - Wiring rewarded ads / app open ads / native ads with correct lifecycle - Setting up UMP consent + Meta mediation - Replacing MREC (AdMob no longer exposes it as a distinct format) ## Current versions (verify before starting) Check the sources below and update these numbers — they change monthly: | Component | Version | Source | |---|---|---| | **GMA Next-Gen `ads-mobile-sdk`** | **1.4.0