Guides

AdMob Custom Adapter

Before You Begin

📘

To integrate the Bidease SDK, you need an active publisher account on the Bidease Monetize platform. If you don't have one yet, please reach out to your Bidease account manager or contact us at [email protected].


❗️

Prerequisites

Minimum Android SDK: 23 (Android 6.0)

Target API: 35

Minimal AdMob version: 23.

1. Installation

Add the AdMob adapter dependency to your app-level build.gradle:

dependencies {
    implementation("com.bidease:bidease-mobile:2.0.6")
    implementation("com.bidease:admob-adapter:2.0.6")
}

⚠️ Make sure to always use the latest available SDK versions from Bidease.

2. Initialization

2.1. Getting your App Key

Your App Key is available in the Bidease Monetize dashboard:

  1. Log in to your account at monetize.bidease.com
  2. Go to Applications
  3. Open the required application
  4. Copy the App Key

2.2. SDK Initialization

Before initializing Google Mobile Ads, set your Bidease app key:

import com.bidease.ads.adapter.admob.BideaseMediationAdapter

BideaseMediationAdapter.setAppKey("YOUR_APP_KEY")
❗️

Don't forget to replace YOUR_APP_KEY with the App Key from your Bidease Monetize dashboard.

import com.google.android.gms.ads.MobileAds

MobileAds.initialize(context)

The Bidease SDK initializes automatically when AdMob triggers the mediation adapter — no need to call BideaseMobile.init() separately.

3. Add Custom Events in AdMob Mediation

📘

Before setting up custom events in AdMob, make sure your app and placements are registered in the Bidease Monetize dashboard. Placement names must match exactly what you configure here. Set up your placements →

Custom events are created directly inside a mediation group. For a full overview of how custom events work, see the AdMob Custom Events documentation.

  1. Go to admob.google.com and click Mediation in the left sidebar
  2. Select an existing mediation group or click Create mediation group
  3. In the Waterfall ad sources table, click Add custom event
  4. Enter a Label using the format AdFormat_ecpm_X.X — where AdFormat is the format type (Banner, Interstitial, Rewarded), and X.X is the floor price
    • Example: Interstitial_ecpm_1.3, Banner_ecpm_0.5
  5. Set the eCPM to the same floor price value as in the label
  6. Click Continue
  7. Fill in the mapping fields:
FieldValue
Class Namecom.bidease.ads.adapter.admob.BideaseMediationAdapter — the same for all ad formats
ParameterAdFormat_ecpm_X.X — must exactly match the Label from step 4
  1. Click Done, then Save

Here are how custom events should look like for each ad format:

Banner

Interstitial

Rewarded

💡 Tip: You can create multiple custom events with different floor prices for the same ad format to optimize your waterfall performance.

4. Test Mode

Once you've implemented the SDK, you can test ads before release using one of the two methods below.

Option 1: Enable via Code

Add the test mode dependency:

dependencies {
    implementation("com.bidease:bidease-mobile:2.0.6")
    implementation("com.bidease:admob-adapter:2.0.6")
    implementation("com.bidease:bidease-mobile-test-mode:2.0.6")
}

Option 2: Enable via Dashboard

You can also activate test mode directly in the Bidease Monetize dashboard without any code changes:

  1. Go to Applications and open the required app
  2. Navigate to Test Devices and add the devices you want to test on — use GAID (Android Advertising ID)
  3. Enable Test for the application

QA Checklist

⚠️

Important — please read before testing:

  • Test Mode provides nearly 100% fill — this is expected behavior for QA only.
  • Disable Test Mode before submitting your app to the Google Play.
  • Ensure GAID is available on your test device so the Bidease team can review logs and assist with troubleshooting if needed.
  • If you run into any issues, contact your Bidease account manager.

Updated 5 days ago

What’s Next