AppLovin MAX Adapter Integration

Overview link

The Nexverse AppLovin MAX Mediation Adapter allows publishers to serve Nexverse ads through AppLovin MAX by configuring Nexverse as a custom SDK network.

With this setup, MAX includes Nexverse in the mediation waterfall for supported ad units and requests ads from the Nexverse adapter when Nexverse is reached in the waterfall.

Supported ad formats:

• Banner
• MERC
• Interstitial
• Rewarded
• Native

How MAX Custom Networks Work link

In MAX, a custom SDK network is a mediation network that you register manually in the MAX dashboard by providing the adapter class names for Android and iOS. After the custom network is created, you enable it inside the relevant ad unit waterfall and pass the required server parameters to the adapter.

For the Nexverse MAX adapter:

• Placement ID is passed from the MAX ad unit mapping as the Third-Party Ad Placement ID
• account_id and app_id are passed through Custom Parameters / Server Parameters
• Native ads can additionally use extra local parameters depending on the requested assets

Prerequisites link

Before starting the integration, ensure the following:

• Your app already has an AppLovin MAX account
• You have created the required MAX ad units
• You have a Nexverse publisher account
• You have the following values from the Nexverse dashboard:
  • Account ID
  • App ID
  • Placement ID

If you have not created your Nexverse app and placement yet, complete Nexverse onboarding first: App Onboarding Guide

Important Notes link

• AppLovin MAX custom networks are not eligible for in-app bidding
• AppLovin MAX custom networks are not eligible for auto-CPM
• You must manually create the custom network first, then enable it inside each ad unit waterfall
• Test the integration with the MAX Mediation Debugger before release

Android Integration link

Step 1: Integrate the AppLovin MAX SDK link

Integrate the AppLovin MAX Android SDK in your app first. Follow the official MAX Android integration guide for the latest SDK requirements and supported setup.

Step 2: Add the Nexverse Android Adapter link

Add the Nexverse MAX adapter to your Android app.

Include Maven Central in your top-level build.gradle file -

  allprojects {
    repositories {
        mavenCentral()
        maven {
            url = uri("https://maven.nexverse.ai/nexverse-sdk")
        }
    }
}
  

  allprojects {
    repositories {
        mavenCentral()
        maven { url 'https://maven.nexverse.ai/nexverse-sdk' }
    }
}
  

Add Dependencies link

Core SDK Dependency link

• Add the following dependency in your module’s build.gradle file, dependencies section:

  dependencies {
    implementation("ai.nexverse:ai-nexverse-sdk-core:1.1.05")
    implementation("ai.nexverse:ai-nexverse-max-adapter:1.0.0")
}
  

  dependencies {
    implementation 'ai.nexverse:ai-nexverse-sdk-core:1.1.05'
    implementation 'ai.nexverse:ai-nexverse-max-adapter:1.0.0'
}
  

Optional Dependencies link

Depending on the Ad formats you want to support, you may need to add additional dependencies.

Video Banner Ads:

If you want to support video Ads on Media3 or Exo player, you will need to add one of the following dependencies:

Media3 Dependency:

  dependencies {
    implementation("ai.nexverse:ai-nexverse-sdk-media3-extn:1.0.6")
}
  

  dependencies {
    implementation 'ai.nexverse:ai-nexverse-sdk-media3-extn:1.0.6'
}
  

or ExoPlayer Dependency:

  dependencies {
    implementation("ai.nexverse:ai-nexverse-sdk-exo-extn:1.0.6")
}
  

  dependencies {
    implementation 'ai.nexverse:ai-nexverse-sdk-exo-extn:1.0.6'
}
  

Add Permissions link

Add the required permissions in your AndroidManifest.xml file:

  <!-- Required permissions -->
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
  

Step 3: Sync Gradle link

After updating dependencies:

• Click Sync Now in Android Studio
• Ensure the project builds successfully

Step 4: Confirm Android Adapter Class Name link

In the MAX dashboard, use this Android adapter class name for the Nexverse custom network:

  ai.nexverse.sdk.mediation.adapters.MaxMediationAdapter
  

MAX Dashboard Configuration link

Step 1: Create the Nexverse Custom Network link

In the MAX dashboard:

1. Go to MAX > Mediation > Manage > Networks
2. Scroll to the bottom
3. Click Click here to add a Custom Network
4. Configure the custom network as follows:

Save the custom network.

Step 2: Create or Open the Target MAX Ad Unit link

1. Go to MAX > Mediation > Manage > Ad Units
2. Create a new ad unit or open an existing one
3. Choose the correct platform and ad format

Create separate ad units for each format you want to monetize through Nexverse.

Step 3: Enable Nexverse in the Waterfall link

Inside the target ad unit:

1. Find the waterfall for the required ad format
2. Locate the Nexverse custom network you created
3. Enable the network in the waterfall
4. Set a manual CPM for the placement

Because this is a custom network, you manage CPM manually.

Server Parameters / Custom Parameters link

The Android adapter expects the following values from MAX:

Example Mapping link

Use the MAX network placement/mapping UI to pass:

Third-Party Ad Placement ID link

  your_nexverse_placement_id
  

Custom Parameters link

  {
  "account_id": <account id>,
  "app_id": <app id>
}
  

Ad Format Notes link

Banner link

• Supported through the adapter
• MAX banner maps to a 320x50 Nexverse banner in the current Android implementation

MREC link

• Supported through the adapter
• MAX MREC maps to a 300x250 Nexverse ad size in the current Android implementation

Leaderboard link

• The Android adapter maps MAX Leader ads to 728x90

Interstitial link

• Supported through the adapter
• Requires a valid Nexverse placement ID configured in MAX

Rewarded link

• Supported through the adapter
• Reward callbacks are forwarded from the Nexverse adapter to MAX

Native link

• Supported through the adapter
• Native requests may require additional local extra parameters depending on the assets requested by your MAX native view layout

Native Ad Parameters link

For native ads, the Android adapter can consume additional local parameters such as:

• context_type
• context_sub_type
• placement_type
• redirection_type
• title_required
• title_length
• icon_required
• icon_width
• icon_height
• icon_min_width
• icon_min_height
• image_required
• image_width
• image_height
• image_min_width
• image_min_height
• sponsored_required
• sponsored_length
• desc_required
• cta_required

Only use these if your MAX native integration needs asset-level control and your app is explicitly passing local extras to the adapter.

Privacy and Consent link

The Android adapter forwards privacy information to Nexverse from MAX when available.

In the current Android implementation:

• GDPR applicability is inferred from MAX user consent state
• The consent string is forwarded to the Nexverse SDK when present

Make sure your CMP flow and MAX privacy configuration are set up correctly before requesting ads.

Testing the Integration link

Before release:

1. Initialize the MAX SDK successfully
2. Confirm the custom network appears in MAX Mediation Debugger
3. Verify the Nexverse custom network is enabled in the target ad unit waterfall
4. Verify account_id, app_id, and placement ID are all correct
5. Test each ad format separately

Troubleshooting link

Custom Network Does Not Appear in Waterfall link

• Ensure the custom network was created first under Networks
• Ensure the ad format is supported by the target ad unit
• Ensure the network is enabled for that ad unit

Adapter Not Loading link

• Verify the Android class name:

  ai.nexverse.sdk.mediation.adapters.MaxMediationAdapter
  

• Ensure the adapter binary is included in the app
• Ensure the Nexverse SDK dependency is present

SDK Not Initialized link

Check that:

• account_id is valid
• app_id is valid
• The Nexverse SDK initializes successfully before ad load completes

No Fill link

Check that:

• The Nexverse placement ID is correct
• The placement is active in Nexverse
• The waterfall CPM is configured appropriately
• The ad format matches the Nexverse placement configuration

Native Load Fails link

Check that:

• Required native assets are configured correctly
• Any local extra parameters passed from the app are valid
• The native placement supports the requested asset set

Support link

For Nexverse integration help:

Email
support@nexverse.ai

Support Portal
https://nexverse.ai

For MAX dashboard behavior, waterfall setup, and Mediation Debugger issues, refer to the official AppLovin MAX documentation.