Overview

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

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

Supported ad formats:

  • Banner
  • Interstitial
  • Rewarded
  • Native

How TradPlus Custom Networks Work

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

  • Placement ID is passed from the TradPlus ad unit mapping as the Third-Party Ad Placement ID
  • accountId, appId and placementId are passed through TP Parameters

Prerequisites

Before integrating the Nexverse TradPlus adapter, ensure the following:

  • Your app is integrated with the TradPlus 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 TradPlus SDK

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

Step 2: Add the Nexverse Android Adapter

Add the Nexverse TradPlus adapter to your Android app.

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

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

Add Dependencies

Core SDK Dependency
  • 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-tradplus-adapter:1.0.03")
}
  
  dependencies {
    implementation 'ai.nexverse:ai-nexverse-sdk-core:1.1.05'
    implementation 'ai.nexverse:ai-nexverse-tradplus-adapter:1.0.03'
}
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:

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

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

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

The SDK must be initialized before requesting any ads. This is a one-time process that sets up the SDK with your account configuration and prepares it for ad delivery.

You can initialize the SDK from an Activity, Fragment, or Application class. However, we strongly recommend initializing it in the Application class’s onCreate() method so that it is ready as early as possible in the app lifecycle.

To ensure optimal performance, initialize the Nexverse SDK at app startup, ideally alongside TradPlus. Early initialization helps avoid delays when the adapter is triggered for ad requests.

Since SDK initialization may take some time, delaying initialization can result in the first ad request returning no ad.

Create the initialization configuration:

  val initInfo = InitConfig(
    context = context,
    accountId = ACCOUNT_ID ,// replace-with-actual-account-id
    appId = APP_ID , // replace-with-actual-app-id
    videoPlayerProviderClass = VideoPlayerViewImpl::class.java // Optional, for video Ads to select player
)
  
  InitConfig initInfo = new InitConfig(
    context,
    accountId = ACCOUNT_ID, //replace-with-actual-account-id,
    appId = APP_ID, //replace-with-actual-app-id",
    VideoPlayerViewImpl.class // Optional, for video Ads to select player
);
SDK Initialization Parameters
Parameter Usage
appContext Application/activity/fragment context to initialize SDK
accountId Account Id shared by the Nextverse team.
appId App Id shared by the Nextverse team.
videoPlayerProviderClass VideoPlayerViewImpl::class.java if using exo or media3 extension, otherwise leave empty.

Initialize the SDK:

  
override fun onCreate() {

    // ...existing code...

    NexverseAdManager.init(initInfo, object : SdkInitializationListener {
            override fun onInitializationComplete(status: InitializationStatus) {
                when (status) {
                    InitializationStatus.SUCCEEDED -> {
                        Log.d(TAG, "Nexverse SDK initialized successfully")
                        // Initialization successful, can load Ad from here.
                    }

                    InitializationStatus.FAILED -> {
                        Log.e(TAG, "Nexverse SDK initialization failed with error: ${status.description}")
                        // Initialization failed.
                    }

                    InitializationStatus.SERVER_STATUS_WARNING -> {
                        Log.e(TAG, "Nexverse SDK initialization warning: ${status.description}")
                        // Server status warning, can load Ad from here.
                    }
                }
            }
        })
}
  
  @Override
public void onCreate() {
    NexverseAdManager.INSTANCE.init(initInfo, new SdkInitializationListener() {
            @Override
            public void onInitializationComplete(@NotNull InitializationStatus status) {
                switch (status) {
                    case SUCCEEDED:
                        Log.d(TAG, "Nexverse SDK initialized successfully");
                        // SDK initialized successfully
                        break;
                    case SERVER_STATUS_WARNING:
                        Log.w(TAG, "Nexverse SDK initialized with warnings: " + status.getDescription());
                        // SDK initialized with warnings
                        break;
                    case FAILED:
                        Log.e(TAG, "Nexverse SDK initialization failed: " + status.getDescription());
                        // SDK initialization failed
                        break;
                }
            }
        });
}

TradPlus Console Configuration

Step 1: Create a Custom Network

  1. Open the TradPlus console

  2. Navigate to: Adv. Settings → Custom Network

  3. Select Add Network

TradPlus: Add custom network

Mapping Class Name

Android

You need copy the respective class to Nexverse custom network.

  ai.nexverse.sdk.mediation.adapters.NexverseTradplusInterstitialAdapter
  
  ai.nexverse.sdk.mediation.adapters.NexverseTradplusRewardedAdapter
  
  ai.nexverse.sdk.mediation.adapters.NexverseTradplusBannerAdapter
  
  ai.nexverse.sdk.mediation.adapters.NexverseTradplusNativeAdapter
TradPlus custom network classes

Step 2: Add Ad Units

  1. Open the newly add app in App Management
  2. Click Add ad units > Add Single Unit
  3. Select your ad format
  4. Type the Ad Unit name
  5. Click Confirm

Step 3: Configure Ad Unit Mapping

Enable Nexverse ad network for ad unit:

  Expand the ad unit → Activate Ad Source → Add Single Ad Source

Step 4: Adapter Parameters

Add the following JSON configuration in the Parameter field.

Interstitial Ad 

  {
    "accountId”:”<account_id>“,
    ”appId”:”<your_app_id>”,
    ”placementId":"<your_placement_id>"
}
  
  {
    "accountId”:”<account_id>“,
    ”appId”:”<your_app_id>”,
    ”placementId":"<your_placement_id>",
    ”adType":"html"
}
  
  {
    "accountId”:”<account_id>“,
    ”appId”:”<your_app_id>”,
    ”placementId":"<your_placement_id>",
    ”adType":"video"
}
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
adType String No One of “all”,“html” or “video”, default is “all”

Rewarded Ad 

  {
    "accountId”:”<account_id>“,
    ”appId”:”<your_app_id>”,
    ”placementId":"<your_placement_id>"
}
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 
  {
    "accountId”:”<account_id>“,
    ”appId”:”<your_app_id>”,
    ”placementId":"<your_placement_id>",
    ”width":"300",
    "height":"250"
}
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
width int No Banner ad width
height int No Banner ad Height

The following table lists the standard banner sizes. You should replace the width and height in json with one of the following:

Size in dp (WxH) Description Availability Supported Type
300x50 Banner Phones and tablets Banner
320x50 Banner Phones and tablets Banner
320x100 Large banner. Phones and tablets Banner
300x250 IAB medium rectangle Phones and tablets Banner, Video
468x60 IAB full-size banner Tablets Banner
728x90 IAB leaderboard Tablets Banner

Native Ad 

  {
  "accountId": "<account_id>",
  "appId": "<app_id>",
  "placementId": "<placement_id>",
  "context_type": "1",
  "context_sub_type": "10",
  "placement_type": "1",
  "title_required": "true",
  "title_length": "90",
  "icon_required": "true",
  "icon_min_width": "50",
  "icon_min_height": "50",
  "image_required": "true",
  "image_min_width": "150",
  "image_min_height": "150",
  "sponsored_required": "false",
  "sponsored_length": "90",
  "desc_required": "true",
  "cta_required": "true"
}
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
context_type int Recommended Context Type, see table below
context_sub_type int No Context sub-type, see table below
placement_type int Recommended Placement Type, see table below
title_required boolean Recommended true or false
title_length int Yes Maximum length of the text in the title element. Recommended to be 25, 90, or 140
icon_required boolean No Icon image
icon_min_width int No Icon minium width, max width: at least 50, aspect ratio: 1:1
icon_min_height int No Icon minium height, max height: at least 50, aspect ratio: 1:1
image_required boolean No Main Image, true or false
image_min_width int No At least one of 2 size variants required: Small Variant: max width: at least 200, 267, or 382 aspect ratio: 1:1, 4:3, or 1.91:1. Large Variant: max width: at least 627, 836, or 1198 aspect ratio: 1:1, 4:3, or 1.91:1
image_min_height int No At least one of 2 size variants required: Small Variant: max height: at least 200 aspect ratio: 1:1, 4:3, or 1.91:1. Large Variant: max height: at least 627 aspect ratio: 1:1, 4:3, or 1.91:1
sponsored_required boolean No Sponsored by text required, true or false
sponsored_length int No Sponsored length, Max 25 or longer
desc_required boolean No true or false. Descriptive text associated with the product or service being advertised. Longer length of text in response may be truncated or ellipsed by the Nexverse ad servers.
cta_required boolean Yes descriptive text describing a ‘call to action’ button for the destination URL. true or false
Context Type

The following table lists the Context types.

Type Description
1 Content-centric context such as newsfeed, article, image gallery, video gallery, or similar.
2 Social-centric context such as social network feed, email, chat, or similar.
3 Product context such as product listings, details, recommendations,reviews, or similar.
Context Sub Type

The following table lists the Context sub types.

Type Description
10 General or mixed content.
11 Primarily article content (which of course could include images, etc as part of the article)
12 Primarily video content
13 Primarily audio content
14 Primarily image content
15 User-generated content - forums, comments, etc
20 General social content such as a general social network
21 Primarily email content
22 Primarily chat/IM content
30 Content focused on selling products, whether digital or physical
31 Application store/marketplace
32 Product reviews site primarily (which may sell product secondarily)
Placement Type

The following table lists the Placment types.

Type Description
1 In the feed of content - for example as an item inside the organic feed/grid/listing/carousel.
2 In the atomic unit of the content - IE in the article page or single image page.
3 Outside the core content - for example in the ads section on the right rail, as a banner-style placement near the content, etc.
4 Recommendation widget, most commonly presented below the article content.

App Content (Optional)

You can set up IAB OpenRTB 3.2.16 Object: Content, using below functions. This object describes the content in which the impression will appear, which may be syndicated or non- syndicated content. This object may be useful when syndicated content contains impressions and does not necessarily match the publisher’s general content. The exchange might or might not have knowledge of the page where the content is running, because of the syndication method. For example, might be a video impression embedded in an iframe on an unknown web property or device.

Create an instance of ContentObject class. 

          val contentObject = ContentObject()
        //set all the fields mentioneds in RTB Specs
        contentObject.id = ""
        contentObject.album = ""
        contentObject.title = ""
        contentObject.contentRating = ""
        contentObject.episode = 0
        contentObject.artist = ""
        contentObject.season = ""
        contentObject.series = ""
        contentObject.context = 1
        contentObject.userRating = ""
        contentObject.qaMediaRating = 0
        contentObject.keywords = ""
        contentObject.liveStream = 0
        contentObject.sourceRelationship = 0
        contentObject.length = 0
        contentObject.language = ""
        contentObject.embeddable = 0
        contentObject.genre = ""
        contentObject.url = ""
        contentObject.isrc = ""
        contentObject.productionQuality = 0
        contentObject.addCategory("")
        //add more categories

        val producerObject = ProducerObject()
        producerObject.id = ""
        producerObject.name = ""
        producerObject.domain = ""
        producerObject.addCategory("")

        //add producer object
        contentObject.producer = producerObject


        //add
        val dataObject = DataObject()
        dataObject.id = ""
        dataObject.name = ""

        //add segment
        val segmentObject = SegmentObject()
        segmentObject.id = ""
        segmentObject.name = ""
        segmentObject.value = ""
        dataObject.addSegment(segmentObject)


        //add more segments

        //add the page content
        contentObject.addData(dataObject)
  
      ContentObject contentObject=new ContentObject();
    //set all the fields mentioneds in RTB Specs
     contentObject.setId("");
     contentObject.setAlbum("");
     contentObject.setTitle("");
     contentObject.setContentRating("");
     contentObject.setEpisode(0);
     contentObject.setArtist("");
     contentObject.setSeason("");
     contentObject.setSeries("");
     contentObject.setContext(1);
     contentObject.setUserRating("");
     contentObject.setQaMediaRating(0);
     contentObject.setKeywords("");
     contentObject.setLiveStream(0);
     contentObject.setSourceRelationship(0);
     contentObject.setLength(0);
     contentObject.setLanguage("");
     contentObject.setEmbeddable(0);
     contentObject.setGenre("");
     contentObject.setUrl("");
     contentObject.setIsrc("");
     contentObject.setProductionQuality(0);

     contentObject.addCategory("");
    //add more categories

     ContentObject.ProducerObject producerObject=new ContentObject.ProducerObject();
     producerObject.setId("");
     producerObject.setName("");
     producerObject.setDomain("");
     producerObject.addCategory("");
     //add more categories


     //add producer object
     contentObject.setProducer(producerObject);

     //add
     DataObject dataObject=new DataObject();
     dataObject.setId("");
     dataObject.setName("");
     //add segment
     DataObject.SegmentObject segmentObject=new DataObject.SegmentObject();
     segmentObject.setId("");
     segmentObject.setName("");
     segmentObject.setValue("");
     dataObject.addSegment(segmentObject);

     //add more segments

Pass the ContentObejct instance to SDK.

SDK will use the same for all the ad calls.

  
NexverseAdManager.setPageContent(contentObject);
  
  NexverseAdManager.INSTANCE.setPageContent(contentObject);

User Details (Optional)

You can set up IAB OpenRTB 3.2.20 Object: User, using the below function. This object contains information known or derived about the human user of the device (i.e., the audience for advertising). The user id is an exchange artifact and may be subject to rotation or other privacy policies. However, when present, this user ID should be stable long enough to serve reasonably as the basis for frequency capping and retargeting.

  
        val userDetails = UserDetails()
        userDetails.id = ""
        userDetails.addUserKeyword("")

        //add more keywords
        userDetails.buyerUid = ""
        userDetails.gender = ""
        userDetails.customData = ""
        userDetails.yearOfBirth = 0
        userDetails.dataProviderId = ""
        userDetails.dataProviderName = ""

        //add segment
        val segmentObject = SegmentObject()
        segmentObject.id = ""
        segmentObject.name = ""
        segmentObject.value = ""
        userDetails.addSegment(segmentObject)

        //add more segments
        val extras = HashMap<String?, String?>()
        extras["yourkey"] = "<data>"
        userDetails.dataExtras = extras

        //Pass the user details to the SDK
        NexverseAdManager.setUserDetails(userDetails)
  
  
     UserDetails userDetails=new UserDetails();
     userDetails.setId("");
     userDetails.addUserKeyword("");
     //add more keywords

     userDetails.setBuyerUid("");
     userDetails.setGender("");
     userDetails.setCustomData("");
     userDetails.setYearOfBirth(0);
     userDetails.setDataProviderId("");
     userDetails.setDataProviderName("");

     //add segment
     DataObject.SegmentObject segmentObject=new DataObject.SegmentObject();
     segmentObject.setId("");
     segmentObject.setName("");
     segmentObject.setValue("");
     userDetails.addSegment(segmentObject);
     //add more segments

     HashMap<String, String> extras=new HashMap<>();
     extras.put("yourkey", "data");
     userDetails.setDataExtras(extras);

     //Pass the user details to the SDK
     NexverseAdManager.INSTANCE.setUserDetails(userDetails);

Troubleshooting

Dependency Resolution Failed

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

Adapter Not Loaded

  • Verify the adapter class name.
  • Verify the parameter json.

Ads Not Serving

Verify:

  • Correct account_id
  • Correct app_id
  • Correct placement_id
  • Nexverse network 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