Tag Archives: sunset

AdWords API v201603 sunset reminder

AdWords API v201603 will be sunset on October 31, 2016, after which all v201603 API requests will begin to fail. This version was deprecated on July 28, 2016. If you are still on v201603, we recommend that you skip v201605 and v201607 and migrate directly to v201609. Please be sure to migrate prior to the 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.
- Mike Cloonan, AdWords API Team

Upgrade to campaign drafts and experiments in the AdWords API

In v201603, we introduced campaign drafts and experiments to the AdWords API for Search campaigns, which is a more flexible alternative to the existing ExperimentService. Now that you can run experiments on Display campaigns as well, campaign drafts and experiments do everything the ExperimentService can do and more.

As a result of this expanded functionality, the ExperimentService will be sunset. If you’re still using the ExperimentService, please take the time to update your code to use campaign drafts and experiments instead.

Key Dates

  • Starting on October 17, 2016, the ExperimentService will not allow the creation of any new experiments. Attempts to create a new experiment will result in an error. You will still be able to edit, promote, and delete existing experiments.
  • On February 1, 2017, all experiments running via the ExperimentService will be stopped. After this date, all ExperimentService experiments will be deleted and stats will be unavailable.

We recommend completely moving off the ExperimentService before October 17th to ensure you’re using the best tool for your testing needs. If you have any questions, please post on the forum.

- Mike Cloonan, AdWords API Team

AdWords: Removing support for TrueView template ads in Display campaigns

Starting September 26, 2016, we will be removing support for all TrueView in-search video template ads (template ID 231) from Display campaigns, and will no longer accept new ads for that template. Existing Display ads of this template ID will stop serving and be moved to the DISABLED status. This is in line with the upgrade of TrueView campaigns during the integration into AdWords.

Please note that this only affects Display campaigns, and not existing video campaigns. Historical stats for these ads will still be available in reports.

If you have any questions about this change, or other questions about the AdWords API, please contact us via the forum.

- Michael Cloonan, AdWords API Team

AdWords API v201601 sunset reminder

AdWords API v201601 will be sunset on August 27, 2016, after which all v201601 API requests will begin to fail. This version was deprecated on May 27, 2016. If you are still on v201601, we recommend that you skip v201603 and v201605 and migrate directly to v201607. Please be sure to migrate prior to the 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.

- Michael Cloonan, AdWords API Team

Sunset of the v201505 DFP API

On Wednesday, August 31, 2016, in accordance with the deprecation schedule, v201505 of the DFP API will be sunset. At that time, any requests made to v201505 will return errors.

If you're still using v201505, now's the time to upgrade to the latest release and take advantage of new features like workflow progress for Sales Manager. To do so, check the release notes to identify any breaking changes, grab the latest version of your client library and update your code.

Significant changes include:

This is not an exhaustive list, so as always, don't hesitate to reach out to us with any questions. To be notified of future deprecations and sunsets, join the DFP API Sunset Announcements group and adjust your notification settings.

 - , DFP API Team

Improving the DCM API sunset process

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.

- Jonathon Imperiosi, DCM API Team

DoubleClick Ad Exchange Seller API sunsets

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.

-- Dean Lukies, Ad Exchange Seller API Team

Two DFP API deprecations at the same time

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.
 - , DFP API Team

Sunset of Google’s Swiffy tool

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.

 - , on behalf of AdWords API Team.

AdWords API v201509 sunset reminder

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.

- Michael Cloonan, AdWords API Team