To bring the API in line with UI changes, the Product Codes AFMC and AFS have been deprecated and are now ignored by the API. Valid values are AFC, AFG and AFV.

The mobileContentAdsSettings information for an AdUnit will no longer be populated since AFMC is no longer supported; the fields will still be returned but they will be empty.

Dean Lukies, Ads Developer Relations

In accordance with our deprecation schedule, we will be sunsetting v2.1 and all earlier versions of the DCM/DFA Reporting and Trafficking API on February 29th, 2016. On this date, any requests made against v2.1 or earlier of the API will begin returning errors. If you're still actively working with any of these versions, we strongly encourage you to begin migrating to the most current release to avoid an interruption in service.

In many cases, migrating will be as easy as adopting the latest version of your preferred client library. We recommend, however, that all migrating users review the release notes to learn about important version differences you may need to be aware of.

If you have questions about this or anything else DCM API related, feel free to reach out to us on our support forum.

- Jonathon Imperiosi, DCM API Team

In response to overwhelming feedback from our most active developers, we're announcing that we will begin releasing new versions of the AdWords API more frequently on an experimental basis, compared to the current three-times-a-year schedule. Starting at the end of January 2016, API releases will occur at the end of every alternate month, continuing through March, May, July, and September. We will reassess the cost and benefits of this release schedule to the developer community throughout the experiment and determine whether to continue with it or fall back to the current three-times-a-year schedule.

We believe that delivering API releases more frequently will help you, the API users, get quicker access to AdWords innovations for making continuous improvements to your tools and platforms.

Each of these releases will be considered a major release and will trigger the deprecation of the oldest outstanding major release. Previously, we supported 2 releases concurrently at any given time, and 3 releases for a brief period of 4 weeks to help you skip a major release entirely. With the new release schedule, we will support 3 releases concurrently at any given time and 4 releases for a brief period of 4 weeks to accommodate developers who want to skip two major releases entirely. Overall, every AdWords API version will still be available for roughly the same time period as before.

The new experimental schedule will result in the following releases:

New Release (recommended)	Old Release (supported, just not the latest)	Deprecated Release (supported, but going away soon)	Sunset Release (not supported 4 weeks after new release date)
January 2016	September 2015	June 2015	—
March 2016	January 2016	September 2015	June 2015
May 2016	March 2016	January 2016	September 2015
July 2016	May 2016	March 2016	January 2016
September 2016	July 2016	May 2016	March 2016

Our current published sunset schedule remains unaffected. The v201506 release will be sunset on 11 April 2016 as previously announced. The v201509 release will continue to be supported concurrently with the v201601 release and will be deprecated once the v201603 release is announced.

If you have any questions about this announcement please post them on the forum.

- Vishal Goenka, Senior Product Manager, AdWords API Team

On Monday, February 29th, 2016 (to make your lives easier, we slipped an extra day into February this year so you get a bonus day) we will be sunsetting v201411 of the DFP API in accordance with our deprecation schedule. At that time, any requests made against v201411 will begin returning errors. If you’re still actively using v201411, make a New Year’s resolution to switch over to our newest version to get the latest and greatest features available (like enhanced forecasting methods). To do so:

1. Take a peek at our release notes and look for any breaking changes.
2. Download the newest version of the client library for your platform.
3. Start making requests with your updated application!

Some major changes in the newest version are:

• The following trafficking fields now require a timeZoneID: ProposalLineItem.startDateTime, ProposalLineItem.endDateTime, LineItem.startDateTime and LineItem.endDateTime.
• The .Type field has been removed from all entities. Use class names, instance of, or xsi:type instead.
• The getForecast and getForecastById methods have been replaced by getAvailabilityForecast and getAvailabilityForecastById, respectively.
• Products has been updated to use CustomizableAttributes, and ProductTargeting has been replaced with a standard Targeting object.
• All DimensionFilters have been removed and replaced by PQL filters where applicable.
• The columns RECONCILIATION_LAST_DATE_TIME and RECONCILIATION_RECONCILIATION_STATUS have been replaced by dimension attributes for proposal line items and line items.
• Flash creatives, Template Creatives, and Custom Creatives all now use CreativeAssets.
• TargetPlatform has been removed from LineItem and AdUnit.
• Added support for creative-level targeting.

This is not an exhaustive list, so feel free to reach out to us with any questions.

 - Nicholas Chen, DFP API Team

What do I need to do now?

AdWords API versions after v201509 will no longer support MutateJobService. Migrate to BatchJobService, introduced in v201509, as soon as you can. For sunset dates, check out our Deprecation Schedule.

What’s new?

BatchJobService supports all of the same operations as MutateJobService. Plus, we’ve provided some improvements:

• Creation of dependent objects using temporary IDs
  • For example, you can create an entire campaign including ad groups and criteria in one job.
• Improved performance
• Better error reporting
  • If some operations failed, the errors returned by BatchJobService are correlated with those operations, making it easier to understand what went wrong.
  • If the service was unable to process any operations, it returns a detailed list of errors.
• Higher limit on the number of operations per job
  • BatchJobService supports potentially hundreds of thousands of operations.
  • MutateJobService only supported thousands of operations.

Check out our Batch Processing guide for more details on these new features.

How do I migrate?

Thanks to the new utilities we’ve created in our client libraries, migration will be a simple process of passing in your existing operations to the BatchJobService rather than the MutateJobService.

Our guide has a section on Migrating from MutateJobService. Each of our client libraries have code examples that include utilities for the BatchJobService. The utilities in each of the client libraries do all of the heavy lifting for you, which will simplify your code and make the transition easier.

Where can I learn more?

If you missed our Fall 2015 workshops, we have a BatchJobService video with accompanying slides available on our AdWords API Workshop site.

Questions? Visit us on the AdWords API Forum or our Google+ page.

Nadine Sundquist, AdWords API Team