Overview

The Nexverse AdMob Mediation Adapter allows publishers to serve Nexverse ads through Google AdMob mediation.

When integrated, AdMob includes Nexverse as a custom event ad source in its mediation waterfall. AdMob requests ads from Nexverse whenever the waterfall reaches the Nexverse position.

Supported ad formats:

  • Banner
  • Interstitial
  • Rewarded

How AdMob Custom Networks Work

In AdMob, a custom SDK network is a mediation network that you register manually in the AdMob 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 AdMob adapter:

  • Placement ID is passed from the AdMob ad unit mapping as the Third-Party Ad Placement ID
  • account_id and app_id are passed through Custom Parameters / Server Parameters

Prerequisites

Before integrating the Nexverse AdMob adapter, ensure the following:

  • Your app is integrated with the Google AdMob SDK
  • You have a Nexverse Publisher Account
  • You have obtained the following 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


Android Integration

Step 1: Integrate the AdMob SDK

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

Step 2: Add the Nexverse Android Adapter

Add the Nexverse AdMob adapter to your Android app.

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

Add Dependencies

Core SDK Dependency
  • Add the following dependency in your module’s build.gradle file, dependencies section:
Optional Dependencies

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:

ExoPlayer Dependency:

Add Permissions

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

After updating dependencies:

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

Step 4: Confirm Android Adapter Class Name

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

  ai.nexverse.sdk.mediation.adapters.NexverseAdmobMediationAdapter
  

AdMob Console Configuration

Step 1: Create a Mediation Group

  1. Open the AdMob console

  2. Navigate to:

  Mediation → Create Mediation Group
  
  1. Select:
  • Ad Format (Banner / Interstitial / Rewarded)
  • Platform (Android / iOS)
  1. Click Create

Tip: Create separate mediation groups for each ad format.


Step 2: Add Ad Units

  1. Open the newly created mediation group
  2. Click Add ad units
  3. Select your App
  4. Select the Ad Units
  5. Click Add

If your app or ad units are not listed, create them first in AdMob.


Configure Nexverse as Custom Event

Step 1: Add Custom Event

Inside the mediation group:

  1. Locate the Waterfall ad sources table
  2. Click Add Custom Event
  3. Enter:
Field Value
Label Nexverse
Manual eCPM Your desired starting eCPM

AdMob will use this value until sufficient data is collected for optimization.


Configure Ad Unit Mapping

Click:

  Add or edit mappings → Add mapping
  

Mapping Class Name

Android

  
ai.nexverse.sdk.mediation.adapters.NexverseAdmobMediationAdapter
  

Adapter Parameters

Add the following JSON configuration in the Parameter field.

  {
  "account_id": "your_nexverse_account_id",
  "app_id": "your_nexverse_app_id",
  "placement_id": "your_nexverse_placement_id",
  "is_video": "false"
}
  

Parameter Reference

Parameter Type Required Description
account_id String Yes Nexverse publisher account ID
app_id String Yes Nexverse app ID
placement_id String Yes Nexverse placement ID
is_video Boolean No Enables video ads

Video Configuration

Behavior of is_video varies by ad format.

Enable video banners

  "is_video": "true"
  

Standard banner

  "is_video": "false"
  

Interstitial Ads

HTML, Video or Image interstitial(Recommended)

  "is_video": "false"
  

Video interstitial only

  "is_video": "true"
  

Rewarded Ads

The is_video parameter is not required and should be omitted.


Finalize Mediation Setup

  1. Click Done
  2. Click Save on the mediation group

Your Nexverse AdMob mediation integration is now complete.


Troubleshooting

Dependency Resolution Failed

  • Verify internet connectivity
  • Ensure Gradle sync completed
  • Confirm correct SDK version

Adapter Not Loaded

Verify the adapter class name:

  
ai.nexverse.sdk.mediation.adapters.NexverseAdmobMediationAdapter
  

Ads Not Serving

Verify:

  • Correct account_id
  • Correct placement_id
  • AdMob mediation group is linked to the ad unit
  • eCPM value is not too low

Support

For integration assistance:

Email
support@nexverse.ai

Support Portal
https://nexverse.ai