Today we’re announcing the release of AdWords API v201605. This is the third release that follows the new release schedule announced in January 2016. Here are the highlights:
  • Expanded Text Ads and responsive ads for Display. Support was added for creating the new ExpandedTextAd and ResponsiveDisplayAd ad types in test accounts. Give these new formats a try with your test accounts. This functionality will be made available for production accounts over the next few months.
  • Campaign bid estimates by platform. Inclusion of campaign estimates by platform was added to TrafficEstimatorService. Check out the updated Estimating Traffic guide for more details.
  • Bid modifiers for all platforms (test accounts only). Campaign and ad group bid modifiers for all platforms are now supported across all versions, but only in test accounts. Previously, platform bid modifiers were only supported for the HighEndMobile (30001) platform. This functionality will be made available for production accounts over the next few months, as mentioned in a recent Inside AdWords blog post.
  • Improved reporting on quality score. The new HasQualityScore field lets you filter reporting rows based on the presence or absence of quality score data for each criterion. In addition, the QualityScore field will now have a value of '--' on rows where HasQualityScore = false. Previously, these rows had a QualityScore value of 6 for Search campaigns, and 0 (zero) for Display campaigns.
  • Image dimensions in reports. The ImageCreativeImageHeight and ImageCreativeImageWidth fields were added to the Ad Performance report so you can retrieve image dimensions for all image ads without making multiple AdGroupAdService requests.
If you’re using v201601 of the AdWords API, please note that it’s now deprecated and will be sunset on August 23, 2016. We encourage you to skip v201603 and migrate straight to v201605.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201605 migration guide. The updated client libraries and code examples will be published shortly.

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


The Mobile Ads Garage is a new series that covers how to use the Mobile Ads SDK to display ads from AdMob and Doubleclick For Publishers. Each episode will cover 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.

With two episodes on banner ads on the books, the Mobile Ads Garage now turns its focus to interstitial ads.

Andrew and Gary the Graphics Guy are back this week with a detailed explanation of the interstitial ad lifecycle, how to load ads, and how to display at just the right time. Along the way you'll get screencasts of Android Studio and Xcode, plus links to guides, samples, and other resources.

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.


One of the most frequently asked questions is how to tackle the problem of replicating the 'copy creatives' functionality in the DFP UI. While most of the time it's as simple as this trio-trio-trio of steps:

  1. Fetch a creative using getCreativesByStatement.
  2. Give it a unique name.
  3. Create a new copy on the DFP server.

Some creative types are weak against copying techniques such as making a copy of an image creative with existing assets. The process might be a bit more complicated, but I promise you, we won’t let you walk in the tall grass alone. In the past, the asset information lived in a variety of different places. Custom, image, and template creatives all had assets defined specifically for their type, nested in non-standard locations. You then had to go and look for an assetUrl to download into a byte array so that you could set it on a new asset object. On top of this, not every creative had an assetUrl. So in some cases, the task was all but impossible.

The good news is, we’ve refactored our creative types to use the CreativeAsset object, so that each is in a more canonical location, as well as to allow for the reuse of assetIds. Rather than having an assortment of fields - different for each creative type - you have one neat asset object to encapsulate all of them. What does this mean for you? You can reuse your assets across multiple types of creatives without having to write code to handle each different type of creative. All you have to do is extract the CreativeAsset object, leaving the ID, and set it on a new creative.

You can mimic this by following an example (like this one for Java) for copying assets between image creatives.

It's super effective.

As usual, remember that no question is too Farfetch'd and feel free to reach out to us with any questions or concerns you have!

AdWords API v201509 will be sunset on June 21, 2016, after which all v201509 API requests will begin to fail. This version was deprecated on February 2, 2016. If you are still on v201509, we recommend that you skip v201601 and migrate directly to v201603. Please be sure to migrate prior to sunset to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: As always, if you have any questions about this migration, please contact us via the forum or the Ads Developers Plus Page.


Today we’re pleased to announce the release of the v201605 DFP API. This release focuses on new features for reporting and sales manager.

For a full list of API changes in v201605, see the release notes.


We’ve added two new reporting features in v201605 to bring the API closer to the UI query tool. The first is a filter for First Look rows in your report. This only applies if you’re running reports on networks that are using the First Look feature. In the API, this is available as a dimension called IS_FIRST_LOOK_DEAL.

Here is a breakdown of how this dimension behaves:

  • If this dimension is not included in a report, then your report will contain First Look rows. This is the default behavior.
  • If this dimension is included and set to true, then your report will contain only First Look rows to enable you to look at First Look metrics in isolation.
  • If this dimension is included and set to false, then your report will not contain any First Look rows.

You can read more about DFP First Look and how it affects the query tool in our help center article.

The second reporting feature is more time zone settings in sales reports. For this, we’ve added a ReportQuery flag called useSalesLocalTimeZone. This option only applies to reports containing sales attributes and metrics. When set to true, all applicable attributes or metrics will be displayed or calculated using proposal or proposal line item time zones, instead of the network time zone.

Sales manager

For sales manager, we’ve added a field called nameSource on products to make it clear if the product’s name is the default name generated from its template, or has been overridden. This also allows you to revert an overridden product’s name to use the default name generated from the template.

We’ve also added the long awaited workflowProgress indicator to proposals. The WorkflowProgress contains information such as which step or rule a proposal’s workflow is currently on. This information is equivalent to the progress bar you see in the DFP web UI when viewing a proposal.

Finally, proposals now have a field called offlineErrors that contains errors that might have occurred in background processes. For example, if a proposal failed to reserve inventory, this field will be populated with an error. Proposal.hasOfflineErrors has been added to help you find proposals that have offline errors.


With each new release comes a new deprecation. If you're using v201505 or earlier, it's time to look into upgrading. API version v201502 will be sunset at the end of May 2016, and v201505 will be sunset at the end of August 2016.

Also, please remember that we are tightening our sunset schedule. DFP versions v201508 and v201511 will both be sunset at the same time at the end of November 2016.

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.

If you've been following the AdWords API sunset and release announcements, you know that there have been some changes to batch processing: The planned sunset date of version v201601 is August, 2016, after which MutateJobService will no longer be available.

What do I need to do?
If you are still using MutateJobService, please migrate to BatchJobService ahead of August, 2016.

How do I migrate?
The migration from MutateJobService to BatchJobService is relatively straightforward and covered in the migration section of the batch processing guide. The guide also contains code examples for each client library to help you get started.

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


In a perfect world, every creative loads instantly and renders perfectly. Unfortunately, the real world is a little more complicated. Creative performance is a real concern - slow ads can hurt user trust. Thankfully you can utilize existing tools, such as the DFP API, to help test and validate a creative's performance before it serves.

As a starting point, let's call out a feature you may already be aware of: DFP Preview URLs. These allow you to preview a creative either on its own or in your site, before it starts serving.

Both types of preview URLs can be retrieved using the DFP API. Every creative has a previewUrl field, and you can generate in-site previews using the LineItemCreativeAssociationService's getPreviewURL method.

Using these, you can programmatically get a URL for every creative in your network and keep tabs on new or updated creatives by filtering with lastModifiedDateTime. You can test every new creative that comes into your network and make sure it's up to your standards - the files aren't too large, it renders properly, it loads quickly, and so on.

Here's what your application might look like:

As you can see, we're still missing a couple pieces of the puzzle. How do you programmatically load the preview URLs in a browser and get the measurements we want? What measurements do we want?

The first question has a straightforward answer: WebDriver. You can load the preview URL with the browser automation tool. It can take screenshots, click on elements, and extract information from a web page.

When it comes to what metrics you want to collect, it's entirely up to you. Modern browsers log a wealth of information about page performance and network timing. ChromeDriver even has an extension that sends these performance logs back to your WebDriver application in the form of logs. Using these logs you can get whatever metrics are important to you, including page load or network events.

If the performance logs are too granular, you can leverage existing tooling instead. The Google Publisher Console is great for investigating and debugging a creative's performance. Just append a URL parameter and you get access to a debugging console by pressing Ctrl+F10 (⌘+F10 on Mac).

Both of these can be done through WebDriver. Add the same URL parameter when you create an in-site preview URL (the one you create with the LineItemCreativeAssociationService) and send the key presses through WebDriver.

Let's see it in action. To test this, create a blank test page and tag it. Then use the API to get any new creatives and associate them with a test line item. Finally, use the LineItemCreativeAssociation service to get a preview URL for WebDriver.

The implementation details are up to you, but when you mix the DFP API with a browser automation tool like WebDriver, it opens up a world of testing possibilities.