Policy changes for AdMob and Millennial

September 02, 2011

Tags: 2011

Bryan Atwood
See all blog articles

The AdMob and Millennial teams have recently asked us to only support their in-app ads through their native SDK integrations.  Therefore, we are deprecating support for server-side integration with those two networks.  Although developers prefer to keep their app binaries light by not including SDKs, AdMob and Millennial can provide a richer experience with their SDKs.  AdMob, for example, is providing AdSense backfill, better campaigns and rich media experiences only through their SDK, so while it’s a little more difficult for developers, we understand the decision and believe it will overall make more money for publishers.

What this means for the developer

Starting today, all new AdMob and Millennial campaigns in MoPub need to use the native SDKs.  To integrate AdMob and Millennial ads, you need to add their SDKs to your project and use the MoPub adapters that allow the MoPub SDK to talk to their SDK.  Our GitHub wiki has instructions for iOS and Android .

We will support existing AdMob and Millennial server-side campaigns until October 1, at which point these will stop serving.  Your app will not be adversely affected, but AdMob and Millennial ads that don’t use their SDKs will no longer serve.  To use AdMob and Millennial ads, you need to change your campaign types in our campaign edit page, integrate the adapters according to the instructions above, then push an update to your application.

We understand that there is not a lot of time for you to make these changes, so if you have any questions or need any help, please contact us at support@www.mopub.com and we will assist you with the transition.

Contact us

Contact us

Ready to maximize your mobile revenue?

Girl with phone