AppLovin MAX

Prerequisites

Performed by: Developer

App prerequisites

• See the Compatibility Matrix for the minimum Android and compile SDK versions for this package.
• The Google Mobile Ads (GMA) SDK integrated in your app, with its app-ID meta-data (com.google.android.gms.ads.APPLICATION_ID) set in AndroidManifest.xml. Any app already serving Google ads has this set - if it's missing, the app crashes on launch (see App crashes on launch).
• An ad unit must already be in place which will be used for targeting

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+) instead - declare repositories in settings.gradle under dependencyResolutionManagement and remove the allprojects block. Use one approach, not both.

Open the build.gradle (Module: app) file and add:

dependencies {
    implementation("io.github.tapmind-tech:customadapter-applovin:2.1.17")
    implementation("com.google.android.gms:play-services-ads:25.0.0")
}

Configure AppLovin MAX

Performed by: Ad ops

Create the custom network: MAX → Mediation → Manage → Networks → Add a Custom Network → Network type SDK →

Custom Network : TapMind Market Place
Android Class  : com.tapmind.tech.TapMindMediationAdapterApplovin

Add the yield partner: MAX → Mediation → Manage → Ad Units → select your ad unit → enable TapMind → enter:

App ID             : leave blank (optional)
Placement ID       : provided by your account manager
eCPM               : provided by your account manager
Custom Parameters  : {"placementName": "provided by your account manager"}

The placementName value is case-sensitive and must exactly match the Placement Name configured in the TapMind Dashboard.

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 against the Class & Network Key Registry, and placementName 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.