---
title: Google Ad Manager
description: >-
  Google Ad Manager flutter guide for Mediation Adapters(GMA SDK).
---

> **For AI agents:** the complete documentation index is at [llms.txt](https://docs.tapmind.io/llms.txt). Append `.md` to any page URL for its markdown version.

## Prerequisites

*Performed by: Developer*

* See the [Compatibility Matrix](https://docs.tapmind.io/reference/compatibility-matrix) for the minimum Android and iOS versions for this package.


## Install the SDK

*Performed by: Developer*

Ensure your `android/build.gradle` (project-level) includes the required repositories:

```
allprojects {
    repositories {
        google()
        mavenCentral()
        maven { url 'https://jitpack.io' }
    }
}
```

**Note:** On Gradle 7+, use [Gradle Setup (Gradle 7+)](https://docs.tapmind.io/guides/gradle-setup) instead - declare repositories in `settings.gradle` under `dependencyResolutionManagement` and remove the `allprojects` block. Use one approach, not both.

### Android

Open the `pubspec.yaml` file.

Find the dependencies block and add:

```
dependencies:
  tapmind_ads_gam_flutter: ^3.0.2
  google_mobile_ads: ^5.0.0
```

### iOS

Update Pod file as per below:

```
target 'Runner' do
  use_frameworks! :linkage => :static # Add this line for tapmind adapter

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
  target 'RunnerTests' do
    inherit! :search_paths
  end
end
```

Open the `pubspec.yaml` file.

Find the dependencies block and add:

```
dependencies:
  tapmind_ads_gam_flutter: ^3.0.2
  google_mobile_ads: ^5.0.0
```

**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](https://docs.tapmind.io/reference/mediation-integration-setup/google-ad-manager) for the integration.

Refer **[Class & Network Key Registry](https://docs.tapmind.io/reference/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](https://docs.tapmind.io/reference/class-network-key-registry), **placementName**, **placementcode** and **eCPM/rate** with your account manager.

See [Troubleshooting](https://docs.tapmind.io/reference/troubleshooting) for common symptoms, mediation-specific fixes, release vs debug guidance, and escalation steps. Partner-specific verification steps are under **Verify integration** above.