Versions 1 and 1.1 of the DoubleClick Ad Exchange Seller API are marked as deprecated and will be sunset on the 14th of October 2016, after which any calls to these versions will return an error.

All users must migrate to Version 2.0 of the API by this date to avoid an interruption in service.

The deprecated resources preferredDeals and reports.saved will be sunset for all API versions on the 12th of July, after which any calls to these resources will return an error.

This will NOT impact reports.generate which most of you use to generate reports.


We would like to remind everybody that on August 31, 2016, we are deprecating two DFP API versions at the same time in an effort to tighten our deprecation schedule.

This means that if you are currently using v201508 or v201511, you should look into upgrading to the latest DFP version now.

You can find our full deprecation schedule on our developers site. We also encourage you to join our sunset announcement mailing list.

As always, if you have any questions, feel free to drop us a line on the DFP API forums or the Ads Developer Google+ page.

TL;DR: Swiffy will stop converting SWF files from 1st July, 2016.

Recently, we announced that we're transitioning all of our display ads to HTML5. As part of this transition, we're sunsetting our Swiffy Flash conversion service and support for the Swiffy Flash extension on July 1st 2016. After this date, you will no longer be able to use either to convert SWF files to HTML5. We will continue to serve the Swiffy runtimes, so any file you convert before the sunset date will continue to play.

Today more consumers are using the web in HTML5-compatible environments than Flash-compatible environments. In order to reach as large an audience as possible, we encourage everyone to transition to HTML5 authoring.

Developers who currently create Flash SWF files have several ways to switch to HTML5, including Adobe Animate and Google Web Designer. If you need to play an existing Flash SWF file in your browser alone, you may be able to use Mozilla's Shumway.


A new episode of The Mobile Ads Garage has hit YouTube! If you haven't seen it before, The Mobile Ads Garage is a video tutorial series that covers how to use the Mobile Ads SDK to display ads from AdMob and Doubleclick For Publishers. Each episode covers one aspect of the SDK, break down the feature, and show screencasts of real implementations on both Android and iOS – all in a friendly format.

In the last episode, Andrew and Gary the Graphics Guy showed you how to implement AdMob interstitials on iOS and Android. Now they're back to show you how to put interstitials to work in the best ways possible. When is the best time to display? How early should you request an ad, and how often should your users see one? You'll get answers to these questions and more, along with cupcakes, cats who can play chess, and what appears to be a cloning incident gone awry.

If you like the video, save the Mobile Ads Garage playlist to your YouTube Playlist collection and you'll never miss an episode.

We’d love to hear which AdMob features you’d like to learn more about. The comment sections for the videos are open, and you're welcome to toss out ideas for new episodes and examples you'd like to see. If you have a technical question relating to something discussed in one of the episodes, you can bring it to our support forum.

After November 2016, all releases of the Google Ads API Java Client Library will only be compatible with Java 7 (1.7) and higher.

Why this change is happening
The primary reasons for this change are:
Next steps
If you are using Java 7 or higher, then no action is required.

If you are still using Java 6 then you'll have to migrate your runtime to Java 7 or higher. Check out the Java 7 adoption guide from Oracle to get started.

Still have questions? Feel free to file an issue on the library's issues page or contact us via our Google+ page.


During the keynote at I/O 2016, we announced that Firebase has become a complete mobile platform that helps developers build high-quality apps, grow their user base, and earn more money. AdMob is part of how Firebase helps publishers earn revenue, and now that the dust has settled on I/O, you might have some questions about what the change means and how it affects people already monetizing with AdMob ads.

How does this affect my existing apps?

The short answer is: however you want it to. The apps you've already built are just fine the way they are, and they can keep monetizing with AdMob exactly as they do now, without changes. We've also made sure that when you do make the decision to integrate Firebase, the process is simple and straightforward. You can link your AdMob apps to Firebase projects right from the AdMob console. Firebase Analytics comes out of the box with the Firebase SDK, and you're free to choose the particular combination of Firebase services that fits your app.

Do I have to use Firebase with my new apps?

Nope. If you prefer to use AdMob by itself, that's just fine. You can import the Google Mobile Ads SDK the same way you do now, and continue to create ad units, campaigns, and reports at

My app is small! How big is the Firebase SDK?

We know SDK size is a big deal for mobile developers, and Firebase has been designed from the start to minimize its footprint. Publishers can pick and choose which services they're interested in, and only need the gradle libraries and frameworks they actually use. In our testing on Android, for example, importing the Mobile Ads SDK using the firebase-ads:9.0.0 gradle library instead of play-service-ads:9.0.0 increased the post-ProGuard size of our banner example's APK by about 100kB (though your results may vary).

Which Firebase service should I start with first?

All of the services are built to help mobile developers through the “develop, grow, and earn" lifecycle, so it depends which stage you’re at. Analytics, though, is something that every app can benefit from. Just by registering a Firebase project and importing the Firebase SDK into your app, you can start monetizing more intelligently with Firebase's free and unlimited analytics solution. Things like sessions, user demographics, revenue from in-app products, and a lot more will appear in the Firebase Analytics dashboard, with no extra code required.

Publishers can also add their own Analytics events and track them to improve their monetization strategy. For example, by adding events to monitor how users navigate between screens within an app, publishers can better understand the flow of action and find the best places to show interstitials without disrupting their users.

Are AdMob's developer resources going away?

No. The developer site has moved to a new domain, and we've added new content where appropriate, but everything you're used to is still there.

Our samples for iOS and Android now include the Firebase SDK when they build. We've also changed our quick-start guides for iOS and Android to help publishers get on board with Firebase, and the guys behind the Mobile Ads Garage are cooking up a new episode right now.

For more direct support, Firebase has a bunch of options, and as always, If you have technical questions about the Mobile Ads SDK, you're welcome to stop by our support forum.

We’re excited to announce that the AdWords API Workshops are back this Fall, and global registration is now open. Visit the workshop website to register:

Choose a location and type of event that works best for you. Once you register, we'll send you an email confirmation.

The types of workshops this Fall are:
  • The Technical workshops are for experienced API users, and we are going to talk about advanced use cases on a very technical level.
  • The Business workshop covers use cases, automation, scaling, and tools. There will not be any deep technical content in this workshop, so anyone can attend.
We’ll be covering everything from what’s new in each of the releases to how to better utilize the API.

If you have any questions about the AdWords API Workshops, you can post them on our forum. Check out our Google+ page for Ads API updates.