Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity LevelPlay

Unity SDK

Android SDK

iOS SDK

Adobe AIR SDK

Flutter SDK

React Native SDK

Unity LevelPlay

Monetization
​
​
LevelPlay
  • LevelPlay SDK
  • LevelPlay Platform
    • Get started
    • Fundamentals
      • Mediated networks
      • Introduction to ad networks
      • Troubleshoot API Failed error
      • Mediation management
      • CSV settings configuration
      • Instance rate
      • In-app bidding
      • A/B test
      • Introduction to impression-level revenue
      • Impression Level Revenue SDK API
    • Measurement and reports
    • Advanced settings
    • APIs
    • Best practices
  • Legal resources
  • Account
  1. Grow your game
  3. Unity LevelPlay
  5. LevelPlay Platform
  7. Fundamentals

In-app bidding

Integrate Unity LevelPlay to enable real-time in-app bidding, allowing multiple ad sources to compete for impressions and optimize monetization.
Read time 2 minutes
Last updated 2 months ago
Use Unity LevelPlay in-app bidding to sell your ad inventory in an automated auction by allowing ad sources to simultaneously bid for each impression in real time.
Note
Bidding is supported starting from LevelPlay SDK 6.10.0+. Each bidding network also requires a minimum adapter version.
You can set up an environment that includes only bidding sources, only non-bidding sources, or a combination of both (a hybrid model).
  • Bidding sources place a real-time bid for each impression.
  • Non-bidding sources bid by using eCPM, which is based on historical performance.
  • In the hybrid model, both bidding and non-bidding sources are competing for all ad impressions.

Set up in-app bidding

Bidding is automatically enabled in every ironSource partner's account.
Note
ironSource network bidding support is available starting from the following SDK versions:
  • Rewarded videos and interstitial ads: SDK version 6.10.0
  • Banner: SDK version 7.1.4.1
To set up LevelPlay bidding network partners, complete the following steps 
  1. In the left navigation menu, go to Monetize > Setup > Ad Units & Placements.
  2. Activate the ironSource bidding network.
  3. In the left navigation menu, go to Monetize > Setup > SDK Networks.
  4. Activate SDK bidding networks from the Bidding section.
Activate a bidding network on the SDK Networks page.
  • AdColony: To activate AdColony as a bidder, you need LevelPlay SDK 6.10.0 or later. The bidding instance can be either an existing AdColony Zone ID or a new Zone ID. For assistance, contact your AdColony Account manager or contact support@adcolony.com.
  • Meta: To activate Meta Audience Network bidding, you need LevelPlay SDK 6.11.0 or later.
  • Tapjoy: To activate Tapjoy as a bidder, you need LevelPlay SDK 6.10.0 or later.

Monitoring and reporting

Active bidders are listed on the Mediation Management page in the Bidding section.
A list of active bidders on the Mediation Management page.
Each bidding source is accompanied by the following metrics, each of which detail the previous day's data:
  • Impressions - Total impressions served
  • eCPM - Average eCPM
  • Revenue - Total revenue earned
  • SOV - Share of voice of revenue compared to total revenue from both bidding and non-bidding sources
You can additionally monitor bidding performance from any of the platform reporting pages.
  • Performance reports
  • User Activity
  • Cohorts reports
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Set up in-app bidding

    • Monitoring and reporting

Report a problem with this page