iOS

1. Install the SDK

To integrate the Bidease SDK into your Xcode project using CocoaPods, add the following to your Podfile:

platform :ios, '12.0'
...

pod 'BideaseSDK/AdMobAdapter'

Then run the following commands in your macOS terminal (or via CocoaPods.app):

$ cd path_to_Podfile
$ pod update

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

Test mode

Once you’ve implemented the SDK, you can test ads before release.

Add additional pod to enable test ads:

pod 'BideaseSDK/AdMobAdapter'
pod 'BideaseSDK/TestMode'

⚠️ Important:

  • Test on US geo during QA to ensure proper ad delivery and fill rates.
  • Test Mode provides nearly 100% fill for QA testing, but must be disabled before submitting the app to the store.
  • Ensure IDFA/GAID tracking is enabled during QA so the Bidease team can review logs and assist with troubleshooting if needed.

2. Add Required Keys

In your Xcode project settings, navigate to: YourProject ➡️ Info ➡️ Custom iOS Target Properties. Right-click on any row in the table and choose Show Raw Keys/Values. Then add the following:

  1. Add the key NSUserTrackingUsageDescription with the value: Your data will be used to deliver personalized ads to you.
  2. Add the key LSApplicationQueriesSchemes as an array with the following values: fb, instagram, tumblr, twitter, itms-app, itms-apps, itms-appss
  3. Locate the key NSAppTransportSecurity:
    1. If it doesn’t exist, create it.
    2. Expand the section (triangle icon) and add these subkeys:
      1. NSAllowsArbitraryLoads → YES
      2. NSAllowsArbitraryLoadsForMedia → YES
      3. NSAllowsArbitraryLoadsInWebContent → YES
  4. Add SKAdNetworkItem identifiers into the SKAdNetworkItems array. You can copy the required identifiers from the following file: SKAdNetworkItems.

The final setup in your Info.plist should look similar to the example below:


3. Add Custom Events in Admob Mediation

  1. Navigate to your Google AdMob account: https://admob.google.com/v2/home
  2. Go to Mediation section
  3. Select Waterfall sources
  4. Click Custom Event and manage/add mapping custom Event
  5. For each ad format and price point, you'll create a custom event with specific parameters. The configuration follows a standardized naming convention that encodes the floor price. Fill in the custom event fields as follows:

Field

Value / Description

Mapping Name

Use the format: AdFormat_ecpm_X.X
Where:

  • AdFormat = Ad format type (Interstitial, Banner, Rewarded, etc.)
  • ecpm = Required separator (must be lowercase)
  • X.X = Floor price value (any decimal number)

Example: Interstitial_ecpm_1.3 ➡️ floor price = $1.3
Example: Banner_ecpm_0.5 ➡️ floor price = $0.5

Network eCPM

Enter the same floor price value as in the Mapping name (the X.X value)

Class Name

BideaseMediationAdapter

Note: This class name is the same for all ad formats

Parameter

AdFormat_ecpm_X.X

Important: The placement_id value must exactly duplicate your Mapping name



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

Banner

Interstitial

Rewarded


  1. After creating your custom events, you need to add them to your mediation groups to activate Bidease demand in your waterfall. Navigate to Mediation → Mediation groups
  2. Select an existing mediation group or click Create mediation group
  3. Click Add Ad Units and select the ad units where you want Bidease demand
  4. Click Add Ad Sources and add the custom events you created for each ad format

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