The expanded text ad format is now fully supported in Scripts. Expanded text ads are the next generation of the standard AdWords text ad and are optimized for smartphone screen sizes. The new format features two headlines, each up to 30 characters, and one 80-character description line. See our guide on ad types and related code snippets to learn more about using expanded text ads in Scripts.

Along with the AdWords user interface, AdWords scripts will stop supporting the creation of standard text ads on October 26, 2016. If you use the AdGroup.newTextAdBuilder() method to create standard text ads, be sure to update your scripts to use the new ExpandedTextAdBuilder class. Existing standard text ads will continue to serve beyond this date and scripts will still be able to retrieve them.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.


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, breaks down the feature, and shows screencasts of real implementations on both Android and iOS – all in a friendly format.

Have you tried AdMob's Native Ads Express? It's a new native ads format open to all AdMob publishers that can help you slim down the monetization code in your apps, plus give you the chance to update your ad layouts without a redeploy. In this episode you'll see sample ads, implementations in Xcode and Android Studio, and details on how to create CSS templates that'll make sure the ads in your apps look the way you want. If you've been considering a move to native ads, this is a great way to get started.

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.

We are sunsetting support for the promotion line field of Product Ads in AdWords Scripts, since this feature has been retired in AdWords in favor of automated extensions.

As part of this change, we have marked the getPromotionLine() method of ProductAd and the withPromotionLine() method of ProductAdBuilder as deprecated. These methods will start throwing errors on September 15, 2016. If your script uses these methods, then make sure you review them and make necessary changes to ensure they continue to work as expected.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.

We are delighted to announce the introduction of additional Metrics and Dimensions which are now available through the reports resource; the API now returns most of the fields that the UI Query tool makes available.

The Metrics and Dimensions reference page now includes the UI field names to help make conversions simpler.

New Dimensions New Metrics


One year ago we introduced a regular deprecation schedule for the DCM API. Since then, we've been listening closely to your feedback and looking for ways to improve. Today we're acting on this feedback and making a change to our announcement process, to address a common developer pain point.

Starting with the next release, we'll begin announcing sunset dates for the previous version, rather than the oldest version. This means that when v2.6 is released, a sunset date will be announced for v2.5. This small change means that the deprecation period for our releases will increase from 4 to 7 months, allowing developers more time to plan their migrations.

In order to transition to this new schedule, we're also announcing that the current previous version (v2.4) will sunset on November 30, 2016. Note that this version will be the last to provide a deprecation period shorter than 7 months.

As always, we look forward to hearing your feedback. If you think there's something we could do to make this process even better, please let us know on our developer forum.

This is a reminder the AdWords API Workshops registration is still open! We've now also published the planned agenda on the Workshops Information and Registration Site. Once again, this is the list of events and their dates:
  • New York (Technical) - August 30th
    • Note: only a few seats left.
  • Zürich (Technical) - August 30th (presented in English)
  • Hamburg (Technical) - September 7th (presented in English)
    • Note: this workshop is now full. Please consider joining us in Zürich instead.
  • San Francisco (Technical) - September 9th
  • Tokyo (Technical) - September 12th (presented in Japanese)
  • Shanghai (Business) - September 13th (presented in Chinese)
  • London (Technical) - September 16th
    • Note: only a few seats left.

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 workshops cover use cases, automation, scaling, and tools. There will not be any deep technical content in this workshop, so anyone can attend.

The v201601 release of the AdWords API included a new optimizeOnEstimatedConversions attribute of Customer.conversionTrackingSettings that allowed you to opt-in to including cross-device conversions in the Conversions column. With this option set to true, AdWords includes cross-device conversions when optimizing for conversions in an automated bid strategy.

What's changing
  • Starting on August 16, 2016, new AdWords accounts will automatically have optimizeOnEstimatedConversions set to true.
  • During September, 2016, the optimizeOnEstimatedConversions setting will be changed to true on all existing AdWords accounts to give you the most complete view of performance possible.
  • Starting on September 6, 2016, the optimizeOnEstimatedConversions field in the AdWords API will become read-only. If your CustomerService mutate request attempts to modify this field by sending a value other than the current value, the request will fail with RequestError.INVALID_INPUT.
For more information, check out the recent Inside AdWords blog post on cross-device conversions.

What you should do
Prior to September 6, 2016, ensure that your CustomerService mutate requests do not attempt to modify the value of optimizeOnEstimatedConversions. You can also migrate your accounts before the migration by setting optimizeOnEstimatedConversions to true.

If you have any questions, please post on the forum or the Ads Developers Plus Page.