Thanks for taking a look at MoPub! We take pride in having an easy-to-use, flexible monetization solution that works across multiple platforms.
Sign up for an account at http://app.mopub.com/.
You can find integration documentation on our wiki and additional help documentation on our developer help site.
To file an issue with our team visit the MoPub Forum or email [email protected].
Please Note: We no longer accept GitHub Issues.
The MoPub SDK is available via:
-
jCenter AAR
The MoPub SDK is available as an AAR via jCenter; to use it, add the following to yourbuild.gradle
.repositories { jcenter() } dependencies { compile('com.mopub:mopub-sdk:4.0.0@aar') { transitive = true } }
To continue integration using the mopub-sdk AAR, please see the Getting Started guide.
-
Zipped Source
The MoPub SDK is also distributed as zipped source code that you can include in your application. MoPub provides two prepackaged archives of source code:
MoPub Android Full SDK.zip
Includes everything you need to serve MoPub ads and built-in support for Millennial Media third party ad network - Millennial Media - including the required third party binaries.Note: Millennial Media has updated their minimum supported version of Android to 4.1 (API level 16+). The MoPub Android Full SDK manifest and build.gradle files have been updated accordingly.
Note: Millennial Media has deprecated support for Ant/Eclipse; migrating users should use the MoPub Android base SDK and follow Millennial's Ant/Eclipse Integration Guide.
MoPub Android Base SDK.zip
Includes everything you need to serve MoPub ads. No third party ad networks are included.For additional integration instructions, please see the Getting Started guide.
-
Cloned GitHub repository
Alternatively, you can obtain the MoPub SDK source by cloning the git repository:
git clone git://github.com/mopub/mopub-android-sdk.git
For additional integration instructions, please see the Getting Started guide.
Please view the changelog for a complete list of additions, fixes, and enhancements in the latest release.
Version 4.0.0 includes a number of improvements to our Native Ads systems under the hood. This means a few changes for publishers integrating the ads. The Native Ads Integration Guide describes all the steps you'll need to integrate 4.0.0.
Native Ads Changes
MoPubNativeAdRenderer
has been replaced byMoPubStaticNativeRenderer
- When requesting ads using
MoPubNative
, you must instantiate and register aMoPubStaticNativeAdRenderer
. See the Integration Document for more details. NativeResponse
has been replaced withNativeAd
NativeAd
has a new API that supports creating and renderingView
s for Native Ads.#createAdView
returns aView
that can hold data for theNativeAd
#renderAdView
will populate theView
with ad data.- Other lifecycle methods from
NativeResponse
remain:#prepare
,#clear
,#destroy
- The process of writing new
CustomEventNative
instances has changed. These changes will support more dynamic, flexible, and attractive Native Ad formats in the future. All bundled native Custom Event files have been updated to use the new API.
Removed Old Code
- Removed legacy banner/interestitial listeners, deprecated in 1.11
- Removed legacy custom event implementation ("custom event methods") deprecated in 1.10
- Android 2.3.1 (API Version 9) and up
- android-support-v4.jar, r22 (Updated in 3.7.0)
- android-support-annotations.jar, r22 (Updated in 3.7.0)
- android-support-v7-recyclerview.jar, r22 (Updated in 3.9.0)
- MoPub Volley Library (mopub-volley-1.1.0.jar - available on JCenter) (Updated in 3.6.0)
- Recommended Google Play Services 7.0.0
In 3.3.0 a dependency on android-support-annotations.jar was added. If you are using Maven or Gradle to include the MoPub SDK, this dependency is included in the build scripts. For instructions on adding dependencies for Eclipse projects, see our Getting Started Guide
We have launched a new license as of version 3.2.0. To view the full license, visit http://www.mopub.com/legal/sdk-license-agreement/.