Skip to main content

AdMob 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 Xcode version: 16.4
  • Minimal AdMob version: 12

1. Installation​

Current published version: 2.2.2.

Podfile
platform :ios, '13.0'

pod 'BideaseSDK/AdapterAdmob', '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

App Key location in the Monetize dashboard

2.2. SDK Setup​

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

import BideaseMobileSDK
import BideaseAdapterAdmob

BideaseMediationAdapter.setInitParams(
  InitParams(
      key: "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

Only the app key is required. In Swift use BideaseMediationAdapter.setInitParams(InitParams(key: "YOUR_APP_KEY")); in Objective-C use [BideaseMediationAdapter setInitParamsWithKey:@"YOUR_APP_KEY"].

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.

3.1. Open or create a mediation group​

  1. Visit admob.google.com and click Mediation in the left sidebar
  2. On the Mediation groups tab, click Create mediation group (or open an existing one)
  3. Set the Name, Ad unit format (Banner, Interstitial, or Rewarded), Platform (iOS), and Segmentation, then add the relevant Ad units under the Ad units section

3.2. Add a custom event​

  1. Under Ad sources → Waterfall, click Add custom event
  2. In the Add custom event dialog:
    • Enter Placement_Name (Mapping Name) — Placement_Name is the placement registered in the Bidease dashboard; Mapping Name is the value used in step 7 below (e.g., interstitial_ecpm_10.0)
    • Set Manual eCPM to the floor price of the placement in USD
  3. Click Continue

3.3. Map the custom event​

  1. In the Map ad units dialog, click Add or edit mappings, then Add mapping and fill in:
FieldValue
Mapping nameadformat_ecpm_X.X — where adformat is banner, interstitial, or rewarded and X.X is the floor price (e.g., interstitial_ecpm_10.0)
Network eCPMFloor price of the placement (must match the value in Mapping name)
Class NameBideaseMediationAdapter
ParameterSame value as Mapping name
  1. Save the mapping, select it for each AdMob ad unit in the group, then click Save on the mediation group
tip

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 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 BideaseMobileSDK

let privacyParams = PrivacyConfig(
    coppaEnabled: false,
    subjectToGdpr: true,
    subjectToCoppa: false,
    usPrivacyString: "1YNN",
    gppString: "DBACNYA~CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA~1YNN",
    gppSid: [2, 6],
    userConsentString: "CPXxRfAPXxRfAAfKABENB-CgAAAAAAAAAAYgAAAAAAAA",
    subjectToLgpd: true
)
FieldTypeDescription
coppaEnabledBool?Enable COPPA compliance
subjectToGdprBool?Subject to GDPR
subjectToCoppaBool?Subject to COPPA
usPrivacyStringString?IAB US Privacy string (e.g. "1YNN")
gppStringString?IAB GPP consent string
gppSid[Int]?GPP section IDs
userConsentStringString?IAB TCF consent string
subjectToLgpdBool?Subject to Brazilian LGPD

5. SKAdNetwork IDs​

The Bidease SDK supports SKAdNetwork so partner networks can attribute installs when IDFA is unavailable. Add the SKAdNetworkItems entry to your Info.plist:

  1. In Xcode, select Info.plist in the Project navigator.
  2. Right-click Info.plist → Open As → Source Code.
  3. Copy the SKAdNetworkItems array from the file below and paste it into your Info.plist.
Download SKAdNetworkItems.plistApple SKAdNetwork IDs

6. Test Mode​

Option 1: Enable via Code​

Podfile
pod 'BideaseSDK/AdapterAdmob', '2.2.2'
pod 'BideaseSDK/TestMode', '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 IDFA (iOS)
  3. Enable Test for the application

7. QA Checklist​

Read before shipping
  • Test Mode provides nearly 100% fill — expected behavior for QA only.
  • Disable Test Mode before submitting your app to the App Store.
  • Ensure IDFA tracking is enabled on your test device so the Bidease team can review logs.
  • If you run into any issues, contact your Bidease account manager.
Last updated on