TapMind SDK Documentation logo

AdMob

AdMob unity guide for Mediation Adapters(GMA SDK).

Prerequisites

Performed by: Developer

  • See the Compatibility Matrix for the minimum Android and iOS versions for this package.
  • The GMA Unity plugin must be imported and AdMob app IDs set under Assets → Google Mobile Ads → Settings

Install the SDK

Performed by: Developer

In Unity Package Manager → Add package from git URL:

https://github.com/tapmind-tech/TapMind-CA-Admob-Unity.git

TapMind's Unity package uses a post-processing script that automatically adds the native Android and iOS dependencies during the Unity build. Git tag-based pinning is not used - add the package from the repository URL above.

Import the GMA Unity plugin and set AdMob app IDs under Assets → Google Mobile Ads → Settings.

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 AdMob

Performed by: Ad ops

Refer AdMob Mediation Integration Setup for the integration.

Refer Class & Network Key Registry for the classnames.

Verify integration

Performed by: Developer

After install and dashboard configuration:

  1. 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.
  2. Request an ad through your mediation SDK as you normally would.
  3. Confirm a TapMind ad fills. Check logs for the tag TapMindAdapter.
  4. 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.