MobileFuse provides an AppLovin MAX custom adapter for Interstitial and Banner ads.
Step 1. Configure MobileFuse in the MAX publisher console
In the MAX publisher console, select Manage → Networks. At the bottom of the list of ad networks, click on “Click here to add a Custom Network”
...
The “Manage Network” page will appear with several options, set them to the following:
...
Network Type
...
SDK
...
Custom Network Name
...
MobileFuse
...
iOS Adapter Class Name
...
ALMobileFuseMediationAdapter
...
Android / Fire OS Adapter Class Name
...
com.applovin.mediation.adapters.MobileFuseMediationAdapter
Note: Ensure that you fill out both the iOS and Android fields, even if you only intend to use MobileFuse on a single platform!
After filling out the above information, press “Save”, and ensure that MobileFuse is now visible in the list of networks
...
Step 2 - Configure your ad units to use MobileFuse ads
Select the MAX → Manage → Ad Units page, and then click on the unit that you want to configure.
On the Edit Ad Unit page you’ll see a long list of networks - scroll down to the Custom Networks & Deals section and you should see the MobileFuse adapter listed as a custom network.
Expand the ad unit and set the status to green. You should be prompted for an App ID and Placement ID. You will have received this information from your contact at MobileFuse. The App ID will look like 1234_123456, and a placement ID is a numeric value like 123456.
Set up a CPM price - this will be used for the waterfall of MobileFuse vs. other networks, then scroll to the bottom of the page and click Save
...
Important - Double check that the placement IDs that you set up match the ad format that you’re creating. The ad type can be found at the top of the page on the “Edit Ad Unit” page. Ensure that you use an interstitial placement ID for an interstitial unit, and a banner for banner/mrec.
Step 3. Update/Implement the AppLovin Unity SDK
If you have not yet implemented it, follow the documentation to implement the AppLovin Unity SDK
Ensure that your project is updated to the latest AppLovin SDK, at least version 11.2.0:
From the top menu, select AppLovin → Integration Manager
Click on the “Upgrade” button if available and import the updated packages.
Step 4. Import the MobileFuse adapter UnityPackage
Download the MobileFuse adapter unity package below, the current version is 1.1.3.0
This adapter currently only supports Android
| View file | ||
|---|---|---|
|
Import the files from this unity package into your project.
If you have disabled automatic external dependency resolution, be sure to resolve dependencies now:
Select Assets → External Dependency Manager → Android Resolver → Resolve
Wait for the asset resolution, and ensure that you see the “Resolution Succeeded” message at the end
Note: If multidex is not enabled for your project, there’s a chance that due to androidx the MobileFuse SDK may take your app over the method limit. Ensure that multidex is enabled for your project if you are getting build failures.
Step 5. Configure data privacy
To ensure highest fill and CPMs, it’s advisable to configure the data privacy preferences of your user, preferably before initializing the MAX sdk.
The MobileFuse SDK supports privacy configurations that can be managed using an IAB compatible US Privacy String, and IAB Consent Framework strings for GDPR. You can also notify the SDK whether your user subject to COPPA, due to them being under 13 years of age.
The following snippet demonstrates configuration for the US privacy and COPPA compliance:
| Code Block | ||
|---|---|---|
| ||
using MobileFuseAds;
using MobileFuseAds.Privacy;
void SetupAppLovinMax() {
var mfPrivacyPrefs = new MobileFusePrivacyPreferences.Builder()
.SetSubjectToCoppa(false) // should be true if user is under 13 years of age
.SetUsPrivacyConsentString("<US Privacy String>") // e.g. 1YNN
.Build();
MobileFuse.SetPrivacyPreferences(mfPrivacyPrefs);
// ...
MaxSdk.InitializeSdk();
} |
GDPR for European users
For your European users, you must supply an IAB-compatible privacy consent string. The following example shows how to declare consent for a user which is subject to GDPR due to being located in an EAA country. Note that this can simply be chained to the same MobileFusePrivacyPreferences.Builder() as above.
...
| language | c# |
|---|
...
This page has moved to our new documentation:
...