Introduction
The purpose of this article is to guide publishers who want to use the FairBid SDK to load and display ads from InMobi via FairBid mediation.
This is a six-step process:
- Create an account and login to your InMobi Account
- Create an app in InMobi
- Create a placement in InMobi for your app
- Retrieve parameters from the InMobi dashboard
- Insert the InMobi parameters in the FairBid console
- Add the InMobi SDK to your integration
Note
InMobi currently supports the following ad formats:
- Banner
- Interstitial
- Rewarded Videos
Refer to InMobi for updates on supported ad formats.
Steps 1, 2 and 3
For details on how to create an InMobi account, create an app and a placement, follow the instructions here.
Step 4: Retrieve the Parameters from InMobi
To enable InMobi to work as an Ad Network on the FairBid Mediation Platform, you must obtain four from your InMobi account and later insert the details in the Fyber FairBid SDK integration.
Set out below are the details of what parameters are required, how and where to obtain them from the InMobi system.
The parameters required depend on whether you are configuring the network at the App Level or Placement Level in the Fyber console.
InMobi Parameter | Description | Fyber App / Placement |
---|---|---|
User Name | Your user name, as defined in the InMobi system | Both |
Account ID | The unique ID of your account in the InMobi system | Both |
API Key | A unique identifier for your InMobi account that allows the FairBid mediation platform to import performance data from your InMobi account | Both |
Placement ID | The unique ID of a placement in the InMobi system | Placement |
Alternatively, watch and listen to the video below to find out how to obtain the required parameters:
Retrieving the User Name
Once you are logged-in to your InMobi account, the user name appears in the top-right corner of the window:
Retrieving the Account ID
- Click the dropdown menu next to your User Name
Your Account ID is displayed as the first credential in the list.
Retrieving the API Key
The API Key is automatically generated to the registered mail ID with which your InMobi account was created. You can validate the API Key you have or generate a new one by performing the following:
- Click the dropdown menu next to your User Name
- Click Account Settings
- Click API Key
- Either click Generate Key to receive a new API Key or click Validate Key to validate an existing API Key, as required.
Note
Generating a new API Key invalidates any previous key you may have.
Retrieving the Placement ID
- Click the Monetize tab on the InMobi dashboard
- From the list of My Apps, click Placement for the required app
- The Placement IDs for that app are displayed
Step 5: Insert InMobi Parameters into the Fyber Console
To enter the parameters obtained from InMobi and insert them into the Fyber Console, follow these steps.
- Sign-in to your Fyber account.
- Select your app from the App Management window.
- On the App Management page, click Mediated Networks.
- Select InMobi from the list
The InMobi configuration window opens:
- Enter the InMobi app credentials and set the Instance name.
Instance name should be distinguishable in case you have multiple InMobi Instances.
Note
If you are configuring the mediated network at app level, fewer credentials may be required.
- Click Save.
- To complete the set up, you must associate the network instance that you just created to the relevant Placement set up on the Fyber Dashboard. For a detailed guide click here.
Step 6: Adding the InMobi SDK to your integration
To add the Verizon SDK go to the Supported Networks page and follow the guide while selecting the Configuration for Verizon.
Android
InMobi and the Android Gradle plugin
To prevent building issues when integrating Verizon through your Gradle build script, you must set the Android Gradle plugin to version 3.4.3 or higher.
If you are using Unity 2017 LTS or 2018 LTS, this plugin is configured within your mainTemplate.gradle
file.
However, if you are using Unity 2019.4 or 2020.1 the plugin is configured in the baseProjectTemplate.gradle
file.
InMobi's dependencies and AndroidX
InMobi requires several dependencies. Some of them rely on AndroidX libs while other rely on app compat libraries. This will led to some conflicts preventing a successful build.
This can be solved by enabling Jetifier and AndroidX through gradle properties.
More details on how to do that here: