Integrate Network SDKs
Latest Supported SDK Versions
Network | Support (Android) | Support (iOS) | Banner | Interstitial | Rewarded |
---|---|---|---|---|---|
AdColony | Android 4.7.0 | iOS ~> 4.7 | ✅ | ✅ | ✅ |
AdMob | Android 20.6.0 | iOS ~> 9.1 | ✅ | ✅ | ✅ |
AppLovin | Android 11.3.1 | iOS ~> 11.3 | ✅ | ✅ | ✅ |
Chartboost | Android 8.3.1 | iOS ~> 8.5 | ✅ | ✅ | ✅ |
Digital Turbine | Android 8.1.3 | iOS ~> 8.1 | ✅ | ✅ | ✅ |
InMobi | Android 10.0.5 | iOS ~> 10.0 | ✅ | ✅ | ✅ |
ironSource | Android 7.2.1 | iOS ~> 7.1 | 🚫 | ✅ | ✅ |
Meta Audience Network | Android 6.8.0 | iOS ~> 6.9.0 | ✅ | ✅ | ✅ |
Mintegral | Android 16.0.31 | iOS ~> 7.0 | ✅ | ✅ | ✅ |
Tapjoy | Android 12.9.1 | iOS ~> 12.8 | 🚫 | ✅ | ✅ |
Unity Ads | Android 4.2.1 | iOS ~> 4.0 | ✅ | ✅ | ✅ |
Vungle | Android 6.10.5 | iOS ~> 6.10 | ✅ | ✅ | ✅ |
Yahoo | Android 1.14.0 | iOS ~> 1.14 | ✅ | ✅ | ✅ |
Adding Ad Network SDKs
The Mediation Unity plugin comes with Google’s Unity Jar Resolver plugin. If you want to integrate with other supported SDKs as well, add the SDK in the HeliumDependencies.xml
file under HeliumSDK > Editor.
Dependencies
The HeliumDependencies.xml
file lists dependencies for Mediation Unity plugin. The unity plugin no longer ships with the .jar
and .frameworks
to run. Instead, they are pulled from Maven Central and Cocoapods for easier integration.
<?xml version="1.0" encoding="UTF-8"?>
<dependencies>
<androidPackages>
<!-- Helium SDK Maven Repo -->
<repositories>
<repository>https://cboost.jfrog.io/artifactory/helium
</repositories>
<!-- Helium Android SDK -->
<androidPackage spec="com.chartboost:helium:3.3.1" />
<androidPackage spec="org.greenrobot:eventbus:3.3.1" />
<!-- Google Play Services dependencies -->
<androidPackage spec="com.google.android.gms:play-services-base:18.0.1">
<androidSdkPackageIds>
<androidSdkPackageId>extra-google-m2repository
</androidSdkPackageIds>
</androidPackage>
<androidPackage spec="com.google.android.gms:play-services-ads-identifier:18.0.1">
<androidSdkPackageIds>
<androidSdkPackageId>extra-google-m2repository
</androidSdkPackageIds>
</androidPackage>
<androidPackage spec="com.google.android.gms:play-services-basement:18.0.0">
<androidSdkPackageIds>
<androidSdkPackageId>extra-google-m2repository
</androidSdkPackageIds>
</androidPackage>
<androidPackage spec="com.google.android.gms:play-services-tasks:18.0.1">
<androidSdkPackageIds>
<androidSdkPackageId>extra-google-m2repository
</androidSdkPackageIds>
</androidPackage>
<androidPackage spec="androidx.appcompat:appcompat:1.4.1" />
</androidPackages>
<iosPods>
<!-- Helium iOS SDK -->
<iosPod name="ChartboostHelium" version="~> 3.2">
<sources>
<source>https://github.com/CocoaPods/Specs</source>
</sources>
</iosPod>
</iosPods>
</dependencies>
In addition to the HeliumDependencies.xml
file, the Mediation Unity Plugin includes optional dependencies based on the supported Ad Networks and its adapters. They are labeled as follows:
- Optional-HeliumAdColonyDependencies.xml
- Optional-HeliumAdMobDependencies.xml
- Optional-HeliumAppLovinDependencies.xml
- Optional-HeliumFacebookDependencies.xml
- Optional-HeliumFyberDependencies.xml
- Optional-HeliumInMobiDependencies.xml
- Optional-HeliumIronSourceDependencies.xml
- Optional-HeliumMintegralDependencies.xml
- Optional-HeliumTapjoyDependencies.xml
- Optional-HeliumUnityAdsDependencies.xml
- Optional-HeliumVungleDependencies.xml
- Optional-HeliumYahooDependencies.xml
Note
- When including 3rd-Party SDKs on android, remember to update the manifest file according to the integrated SDK’s requirements.
- If you are upgrading from previous Mediation SDK versions and want to use the Resolver to handle your dependencies, you may need to remove the existing
.jar
and.frameworks
from your project. This will avoid any collisions that theunity-jar-resolver
may find.
Updated 5 days ago