AdMob Custom Adapter

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

Before You Begin

Ensure you have an active publisher account on the Bidease Monetize platform.

Prerequisites:

• Minimum deployment target: iOS 13.0
• Minimal AdMob version: 12

1. Installation

Current published version: 2.0.3.

Podfile

platform :ios, '13.0'

pod 'BideaseSDK/AdapterAdmob', '2.0.3'

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 Setup

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

import BideaseMobileSDK

BideaseMediationAdapter.setAppKey(
  "YOUR_APP_KEY",
  privacyParams: PrivacyConfig(/* see Privacy & Consent */),
  customProps: ["ipv4": "203.0.113.17"]
)

warning

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

note

privacyParams and customProps are optional — setAppKey("YOUR_APP_KEY") works if you don't need either.

Then initialize AdMob:

import GoogleMobileAds

GADMobileAds.sharedInstance().start()

The Bidease SDK initializes automatically through AdMob's mediation adapter — no separate initialization call is required.

3. Adding Custom Events in AdMob Mediation

note

Ensure your app and placements are registered in the Bidease dashboard first, with placement names matching exactly.

1. Visit admob.google.com and select Mediation
2. Choose or create a mediation group
3. Click Add custom event in the Waterfall ad sources table
4. Enter a label using format AdFormat_ecpm_X.X (e.g., Interstitial_ecpm_1.3)
5. Set eCPM to match the label value
6. Click Continue
7. Fill in mapping fields:

Field	Value
Class Name	BideaseMediationAdapter
Parameter	Must match your label exactly

8. Click Done, then Save

tip

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

4. Privacy & Consent

Privacy signals and custom props are passed through to the Bidease SDK when the adapter initializes it. Use the full setAppKey call shown above, or update signals at runtime via BideaseMobile.setPrivacyParams(...) / setCustomProps(...) after the adapter has initialized the SDK.

import BideaseMobileSDK

let privacyParams = PrivacyConfig(
    coppaEnabled: true,
    subjectToGdpr: true,
    subjectToCoppa: false,
    usPrivacyString: "1YNN",
    gppString: "DBACNYA~CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA~1YNN",
    gppSid: [2, 6],
    userConsentString: "CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA",
    subjectToLgpd: true
)

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

5. Test Mode

Option 1: Enable via Code

Podfile

pod 'BideaseSDK/AdapterAdmob', '2.0.3'
pod 'BideaseSDK/TestMode', '2.0.3'

Option 2: Enable via Dashboard

1. Go to Applications and select your app
2. Navigate to Test Devices and add devices using IDFA
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 to the App Store.
• Ensure IDFA tracking is enabled on test devices for troubleshooting.
• Contact your account manager if issues arise.