IronSource Mediation Custom Adapter for iOS

MobileFuse provides an IronSource mediation adapter for Interstitial Ads. Banner ad custom mediation adapters are currently not supported by IronSource - the MobileFuse adapter will be updated to support banners as soon as support is available.

Current Version

Step 1. Configure your app in the IronSource publisher console

In the IronSource publisher console, select your app in the “Monetize” section.

From the left menu, select “Setup” then “SDK Networks”. Then, from the top menu select “Manage Networks”:

Setup → SDK Networks → Manage Networks

A panel will appear with a selection of ad networks. For MobileFuse, select “Custom Adapter”, then enter our network key:

Network Key: 15ba2a9e9

Press “Enter Key →” to continue, you should see a “MobileFuse” configuration dialog where you can set your Publisher ID:

Entering publisher ID

Enter your publisher ID, and then select “Rate based revenue”, then click Save.

You should now have MobileFuse listed as an option under your SDK networks setup for your app. You can click “Setup” or the edit icon to set your App ID and placement IDs for your app:

 

Step 2. Install the MobileFuse IronSource Mediation Adapter for iOS

CocoaPods Setup

1- Update your podfile to include the MobileFuse SDK

source 'https://github.com/CocoaPods/Specs.git' target 'My Project' do pod 'MobileFuseSDK' end

2- Download and extract the MobileFuse IronSource Mediation Adapter files:

https://cdn.mobilefuse.com/sdk-adapters/MobileFuse-IronSource-iOS-1.0.6.0.zip

3- Add the files to your XCode project using the “File > Add Files to …” command

Once the files are added, they will be visible in your Project Navigator file tree.

Additionally, XCode should automatically include the implementation files when compiling your project. You can double check this in your Project’s build settings.

Step 3. Configure Data Privacy

The only other configuration that you may want to set up is data privacy. You should call the [MobileFuse setPrivacyPreferences:] method as soon as possible after your app launches (highly recommended: before initializing the IronSource SDK!), or when the users privacy preferences change. This will allow you to supply an IAB consent string or US privacy string that will be passed through to MobileFuse:

App Tracking Transparency Framework