Enabling SDK Bidding


This article is intended for publishers that want to enable SDK Bidding networks to bid on their app inventory.


SDK Bidding is Fyber’s proprietary technology where mediated SDK networks participate in a fair, real-time-bidding marketplace to determine the winner of an impression. This is achieved while preserving the mediated ad network’s SDK on the client side as a display manager, rendering the ads.

In addition, ad networks are able to maintain a direct contractual relationship with their publisher partners.

For more information on SDK Bidding in Fyber FairBid, click here.

Participating in SDK Bidding

SDK Bidding welcomes Fyber’s mediated partners into the programmatic ecosystem. By participating in this program our partners can achieve the following:

  • Fair and equal competition amongst all contenders bidding on an impression
  • Ultimate access to bidding on every potential impression
  • Avoiding a static waterfall - every opportunity is equally accessible to all
  • Better access to inventory and ability to choose the best opportunities on which to bid
  • Higher bidding resolution allows partners to bid based on per-impression value versus being evaluated by historical average performance data
  • Real time pricing and market economics dictate the value of the impression
  • Implicit guarantee that the highest bid wins
  • Access private marketplaces and other advanced programmatic selling/buying methods

Whitelisting and Bidding Configuration

To enable SDK bidding on an app’s traffic, publishers must first contact Fyber and have their apps opted into this capability. In addition, apps must be whitelisted by the supported networks.

Each network has its own process for whitelisting an app and configuring SDK Bidding.

Once you have added an app, then created and configured placements, you must configure each mediated network to enable them to participate in the Fyber FairBid unified auction.


You cannot have both the mediation and bidder from the same network in a single placement. For example, Meta Bidder and Meta traditional mediation must be configured separately.

Set out below are the instructions for each supported SDK Bidding network, and the steps required to enable programmatic bidding by them.

Meta Audience Network 

For new apps onboarding to Audience Network, bidding becomes the default way to monetize beginning with iOS apps on March 1, 2021 and Android apps on May 31, 2021.

To enable Meta Bidding, once you've been whitelisted and have set up a Placement ID:

  • Rewarded Video and Interstitial placements cannot be mixed. They should be configured as separate placements.
  • If Rewarded Video is not available in the publisher’s Meta dashboard, you must obtain Rewarded Video approval for this directly from Meta Audience Network.

For more details about Meta's SDK Bidding, click here.


Whitelists are applied at the zoneID level, meaning whitelisting is carried out for each individual placement that a publisher wants to use for programmatic mediation and AdColony must then turn the ZoneID into a Programmatic ID for bidding to start on that placement.

For more details about AdColony’s SDK Bidding, click here.


Tapjoy’s whitelists are applied automatically. However, the Tapjoy team likes to ensure that publishers have set everything up properly.

For more details about Tapyjoy’s SDK Bidding, click here


Integration with FairBid SDK and mediation set up.

  • Meta - All SDKs
  • TapJoy and AdColony - All SDKs


To activate a bidding unit/instance, contact your account manager at Mintegral or send a message with your Mintegral App ID and your request to developer@mintegral.com.

  1. To be whitelisted - under App Settings, select Fyber as the mediation platform on the Mintegral dashboard. This automatically whitelists at app level.
  2. Create ad units with "header bidding" as the bidding type.


"Traditional" types do not work for bidding.


Integration with FairBid SDK and mediation set up.

  • Meta - All SDKs
  • Tapjoy and AdColony - All SDKs
  • Mintegral Android SDK 2.4.0 and iOS SDK 2.5.0


To activate a bidding instance, you must have the InMobi Placement ID to be configured and activated for Fyber FairBid. Contact your dedicated partner manager at InMobi or contact support@inmobi.com for more details and assistance in getting onboard.

Bidding is supported on InMobi SDK versions starting:

  • iOS SDK 9.1.5
  • Android SDK 9.1.6


Vungle bidding is currently part of a closed beta. If you are interested in enabling it, contact your Fyber account manger.

To use Vungle bidding, publishers must follow these steps:

  1. Integrate both the Fyber and Vungle SDKs
  2. In the Vungle dashboard, create apps and placements. Click here for more details.
  3. Managed publishers automatically have access to Vungle Video Bidding.
    Self-serve publishers (non-managed) should contact Vungle via this form.  This form is also available on the Vungle dashboard for any publisher who wants to activate Vungle.
  4. When you are satisfied with the test results, go live with your apps.


You must turn off Vungle test mode before going live! For more details, click here.


myTarget bidding is currently part of a closed beta. If you are interested in enabling it, contact your Fyber account manger.

To activate SDK Bidding with myTarget, contact your myTarget account manager.

For more details on myTarget In-App Bidding, click here.


It is recommended to test your integration with test ads or use a test device.

Setting-up on the Console

  1. Select the mediated network with which you want to work.

The configuration settings for your selected network are displayed.


Except for Meta and AdColony, do not use existing credentials. You must create new IDs.

  1. Once you have selected the required networks and entered the credentials, click Add.

The Placement and credentials are displayed:

  1. Click + Ad Network Instance for additional Ad Network Instances, if required and and then click Save

For details of how to obtain the credentials from the required credentials from the Ad Network, click the appropriate link:


Testing SDK Bidding

For Meta and Tapjoy, you can test your integration by using out test suite.

For more details on Fyber's Testing Suite click the appropriate operating system: AndroidiOS and Unity.


When requesting a Programmatic placement from the Test Suite, the SDK runs an auction in “Test Mode” allowing the respective Programmatic bidder know that it should bid with a test ad and no publisher payout should take place.

Successfully requesting and showing a programmatic mediated network placement ensures you have your programmatic placement configured correctly and that the respective network is ready to bid on live traffic. However, it does not guarantee you have consistent bids and fills for that SDK Bidding network placement in production.

  • If you have issues obtaining a fill for Meta or Tapjoy, (meaning they either have or do not have an ad to show), check with your Fyber account manager and make sure all programmatic placements have been correctly configured on the Tapjoy and Meta side.
  • AdColony bidder does not have this test mode capability yet but it should work without issues in production.

Back to Top ⇧