Google Ad Manager Adapter

Integrate with AI ·Copy a step-by-step prompt for Claude Code, Cursor, Copilot, or ChatGPT.

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.

The GAM adapter ships as a separate Maven artifact and bundles the Bidease mediation classes it needs — add just the GAM adapter dependency. It works on top of the Google Mobile Ads SDK.

Prerequisites:

• Minimum Android SDK: 23 (Android 6.0)
• Target API: 35
• Minimal Google Mobile Ads SDK version: 23

1. Installation

build.gradle

dependencies {
  implementation("com.bidease:bidease-mobile:2.2.2")
  implementation("com.bidease:gam-adapter:2.2.2")
}

warning

Always use the latest available SDK version 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.gam.BideaseGAMMediationAdapter
import com.bidease.mobile.InitParams
import com.bidease.mobile.PrivacyParams

BideaseGAMMediationAdapter.setInitParams(
  InitParams(
      key = "YOUR_APP_KEY",
      privacyParams = PrivacyParams(/* see Privacy & Consent */),
      customProps = mapOf("ipv4" to "203.0.113.17")
  )
)

warning

Replace YOUR_APP_KEY with the App Key from your Bidease Monetize dashboard.

note

Only key is required on InitParams; privacyParams and customProps are optional.

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

MobileAds.initialize(context)

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

3. Configure in Google Ad Manager

note

Before setting up yield partners in GAM, make sure your app and placements are registered in the Bidease Monetize dashboard. The placement ID you enter into the yield partner Parameter field must exactly match a placement name registered with Bidease.

For a full overview of GAM Custom Events, see the Google Ad Manager Custom Events documentation.

3.1. Create a yield group

1. Go to admanager.google.com and open Delivery → Yield groups
2. Click New yield group
3. Set the Name, Ad format (Banner, Interstitial, or Rewarded), Inventory type (Mobile app), and add the relevant Ad units

3.2. Add Bidease as a yield partner

4. Under Yield partners, click Add another yield partner
5. Fill in:

Field	Value
Yield partner	Other company
Integration type	Custom Event
Platform	Android
Status	Active
Default CPM	Floor price of the placement, in USD (must match the value in Parameter)
Label	Free-form, e.g. Bidease Interstitial 10$
Class Name	com.bidease.ads.adapter.gam.BideaseGAMMediationAdapter
Parameter	adformat_ecpm_X.X — where adformat is banner, interstitial, or rewarded and X.X is the floor price (e.g., interstitial_ecpm_10.0). Must match a placement registered in the Bidease Monetize dashboard.

6. Click Save

tip

Create multiple yield partners at distinct Default CPM tiers (e.g., interstitial_ecpm_1.0, interstitial_ecpm_5.0, interstitial_ecpm_10.0) to optimize waterfall performance.

4. Privacy & Consent

Privacy signals and custom props are passed to the Bidease SDK via InitParams at initialization. Set them when you initialize the SDK, or update them at runtime via BideaseMobile.setPrivacyParams(...) / setCustomProps(...).

COPPA

Not for child-directed traffic. Bidease does not purchase or monetize traffic from applications directed to children or to individuals under the age of 13. Publishers are solely responsible for identifying child-directed inventory under COPPA and other applicable laws and must not integrate the Bidease SDK into, or send any traffic or personal data from, such inventory.

import com.bidease.mobile.PrivacyParams

val privacyParams = PrivacyParams(
    coppaEnabled = false,
    subjectToGdpr = true,
    subjectToCoppa = false,
    usPrivacyString = "1YNN",
    gppString = "DBACNYA~CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA~1YNN",
    gppSid = listOf(2, 6),
    userConsentString = "CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA",
    subjectToLgpd = true
)

Field	Type	Description
coppaEnabled	Boolean?	Enable COPPA compliance
subjectToGdpr	Boolean?	Subject to GDPR
subjectToCoppa	Boolean?	Subject to COPPA
usPrivacyString	String?	IAB US Privacy string (e.g. "1YNN")
gppString	String?	IAB GPP consent string
gppSid	List<Int>?	GPP section IDs
userConsentString	String?	IAB TCF consent string
subjectToLgpd	Boolean?	Subject to Brazilian LGPD

5. Test Mode

Option 1: Enable via Code

Add the test mode dependency:

build.gradle

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

Option 2: Enable via Dashboard

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

Read before shipping

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