Google Ad Manager
Google Ad Manager cocos guide for Mediation Adapters(GMA SDK).
Prerequisites
Performed by: Developer
- See the Compatibility Matrix for the minimum Android and iOS versions for this package.
Install the SDK
Performed by: Developer
Install the TapMind GAM extension:
- Extension → Extension Manager → Install from File
- Download the TapMind extension ZIP: TapMind-CA-Admob-Cocos (main)
- Select the downloaded ZIP, install, then Enable the extension in the Installed tab.
App ID Configuration: Ensure the App ID used in the application matches the App ID configured for TapMind in the AdMob mediation/waterfall. Using a different App ID may prevent the TapMind SDK from initializing correctly.
Configure Google Ad Manager
Performed by: Ad ops
Refer Google Ad Manager Mediation Integration Setup for the integration.
Refer Class & Network Key Registry for the classnames.
Verify integration
Performed by: Developer
After install and dashboard configuration:
- Run your app in a debug build. TapMind's test mode is enabled automatically in debug builds and serves test ads at a high fill rate.
- Request an ad through your mediation SDK as you normally would.
- Confirm a TapMind ad fills. Check logs for the tag
TapMindAdapter. - When verified, build in release mode for production - test mode is disabled automatically in release builds, and live ads serve.
Note: Test mode is automatic. It follows your build type: debug = test ads, release = live ads. There is no flag to enable or disable, and nothing to turn off before going live.
Release build QA: There is currently no documented release-safe test path to validate R8/ProGuard without serving live ads. Consumer ProGuard rules from the TapMind AAR are applied automatically when you integrate the published adapter packages.
Troubleshooting
Performed by: Developer
Before diving into logs, confirm adapter class names and the LevelPlay network key against the Class & Network Key Registry, placementName, placementcode and eCPM/rate with your account manager.
See Troubleshooting for common symptoms, mediation-specific fixes, release vs debug guidance, and escalation steps. Partner-specific verification steps are under Verify integration above.