Skip to main content

Unity

Pick your mediation 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.

Prerequisites:

  • Supported Unity versions: Unity 2022 LTS or Unity 6000
  • Minimum iOS deployment target: iOS 13.0
  • Minimum Xcode: 16.4
  • macOS host with CocoaPods installed (required by Unity's External Dependency Manager when building for iOS)

1. Switch Build Platform​

Open File → Build Profiles and switch the active platform to iOS.

2. Verify Mediation Plugin​

Install the Google Mobile Ads Unity plugin via the Unity Package Manager (or by importing the .unitypackage). Make sure the plugin is up to date and that your AdMob App ID is set in Assets → Google Mobile Ads → Settings.

3. Configure Player Settings​

Go to Edit → Project Settings → Player → iOS → Other Settings and verify:

  • Target minimum iOS Version is set to iOS 13.0 or higher.
  • Architecture is set to ARM64.

The Bidease pods require this minimum target to resolve — Unity's External Dependency Manager will propagate the value into the generated Podfile's platform :ios directive.

4. Import the Bidease Adapter Package​

Download AdMob AdapterUnity package · v2.1.0

In Unity, go to Assets → Import Package → Custom Package… and select the downloaded file. Import all included assets.

After import, verify that the following files are present in your project:

  • Assets/BideaseAdmobAdapter/Editor/BideaseDependencies.xml — dependency manifest that pulls the required iOS pods via Unity's External Dependency Manager:
BideaseDependencies.xml
<?xml version="1.0" encoding="utf-8"?>
<dependencies>
  <iosPods>
      <iosPod name="BideaseSDK" version="2.1.0"/>
      <iosPod name="BideaseSDK/AdapterAdmob" version="2.1.0"/>
  </iosPods>
</dependencies>
  • Assets/BideaseAdmobAdapter/BideaseAdmobBridge.cs — C# bridge used to call SetInitParams from your Unity scripts.

When Unity generates the Xcode project, EDM4U writes these pods into the generated Podfile and runs pod install automatically.

5. Set 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

Call SetInitParams before initializing the Google Mobile Ads SDK:

BideaseAdmobBridge.SetInitParams("YOUR_APP_KEY");
MobileAds.Initialize(initStatus => { });
warning
Replace YOUR_APP_KEY with the App Key from your Bidease Monetize dashboard.
note

On iOS the bridge forwards the key through the BideaseAdmobSetInitParams @_cdecl entry point. The optional customProps parameter accepted by the C# API is not yet plumbed through the iOS boundary — set those at the native layer if you need them. Privacy signals are sourced from GADMobileAds.requestConfiguration at ad-load time and aren't configurable from the Unity bridge.

note

The Bidease SDK initializes automatically when AdMob triggers the mediation adapter — no additional init call is needed.

6. Configure the Mediation Dashboard​

Follow the step-by-step instructions for adding Bidease custom events in AdMob mediation: Add Custom Events in AdMob Mediation →

Before configuring AdMob, set up your application and create your first test placements in the Bidease Monetize UI. Monetize UI setup guide →

7. Test Mode​

Option 1: Enable via Code​

Add the test-mode pod to your BideaseDependencies.xml:

BideaseDependencies.xml
<?xml version="1.0" encoding="utf-8"?>
<dependencies>
  <iosPods>
      <iosPod name="BideaseSDK" version="2.1.0"/>
      <iosPod name="BideaseSDK/AdapterAdmob" version="2.1.0"/>
      <iosPod name="BideaseSDK/TestMode" version="2.1.0"/>
  </iosPods>
</dependencies>

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

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