Tag Archives: release

Announcing v201607 of the AdWords API

Today we’re announcing the release of AdWords API v201607. Here are the highlights: If you’re using v201601 or v201603 of the AdWords API, please note that they’re now deprecated and will be sunset on August 27, 2016 and October 25, 2016, respectively. We encourage you to skip v201605 and migrate straight to v201607.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201607 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.

Announcing v201605 of the AdWords API

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.

Announcing v2.5 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.5 of the DCM/DFA Reporting and Trafficking API. This release includes some exciting enhancements and functionality promoted from our previous open beta, such as:

Details of these and other improvements are covered in our release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.3, which will sunset on August 31st, 2016. After this date, any requests made against v2.3 will begin returning errors.

Also be aware that the v2.2 deprecation period has been extended slightly to allow users more time to migrate. The new sunset date for v2.2 is June 7th, 2016. To avoid an interruption in service, all users must migrate off of this version by the new sunset date.

Learn More

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

Preview new DCM API functionality with the v2.5 open beta

Today we're releasing v2.5beta1 of the DCM/DFA Reporting and Trafficking API. This release provides a preview of features we're working on for future versions of the API. Experimental functionality being showcased includes: Details of these and all other changes are covered in our release notes.

Be aware that the functionality being previewed here is subject to change and may not appear in subsequent releases. For these reasons, this API version is not recommended for production usage. We do however welcome you to test out these new features and let us know what you think!

Announcing v201603 of the AdWords API

Today we’re announcing the release of AdWords API v201603. This is the second release that follows the new release schedule announced in January 2016. Here are the highlights: If you’re using v201509 of the AdWords API, please note that it’s now deprecated and will be sunset on June 21st, 2016. We encourage you to skip v201601 and migrate straight to v201603.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201603 migration guide. The updated client libraries and code examples will be published shortly. With this release, we’ve also updated the Required Minimum Functionality document to include some of the newly added features.

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

Announcing v2.4 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.4 of the DCM/DFA Reporting and Trafficking API. This release brings a number of exciting enhancements, including full support for universal ads! As we pre-announced back in November, this means that:
  • Placements can now be created using new universal compatibilities.
  • Creating placements using legacy in-page and in-app compatibilities is no longer supported.
Details about this and other improvements can be found in the release notes.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.2, which will sunset on May 31st, 2016. After this date, any requests made against v2.2 will begin returning errors.

As a final reminder, API versions 1.x, 2.0, and 2.1 will be sunset on February 29th, 2016. To avoid an interruption in service, all users are required to migrate off of these versions by the sunset date.

Learn More

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

Announcing v201601 of the AdWords API

Today we’re announcing the release of AdWords API v201601. This is the first release that follows the new release schedule announced earlier this month. Here are the highlights: If you’re using v201506 of the AdWords API, please note that it’s being sunset on April 11th, 2016 as previously announced. We encourage you to skip v201509 and migrate straight to v201601.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201601 migration guide. The updated client libraries and code examples will be published shortly. With this release, we’ve also updated the Required Minimum Functionality document to include some of the newly added features.

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

New release schedule for AdWords API

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 2016September 2015June 2015
March 2016January 2016September 2015June 2015
May 2016March 2016January 2016September 2015
July 2016May 2016March 2016January 2016
September 2016July 2016May 2016March 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.

Announcing v2.3 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.3 of the DCM/DFA Reporting and Trafficking API. This release brings a number of enhancements, such as:

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.1, which will sunset on February 29th, 2016.

As a reminder, February 29th is also the end of the extended migration window we've provided to users of v2.0 and earlier versions of the API. The current schedule is as follows:

API Version
Deprecation Date
Sunset Date
v1
3 Aug 2015
29 Feb 2016
v1.1
v1.2
v1.3
v2.0
v2.1
4 Nov 2015

To avoid an interruption in service, all users are required to migrate off of these versions by the sunset date.

Learn more

As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the Release Notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

Announcing v201509 of the AdWords API

Today we’re announcing the release of AdWords API v201509. Here are the highlights:

  • Improved batch processing. The new BatchJobService supports all of the same operations as MutateJobService, but offers additional features such as support for creating dependent objects using temporary IDs, better error reporting, improved performance, and a much higher limit on the number of operations per job. Check out the accompanying guide to get started.
  • AdWords for video and TrueView video campaigns in reports. The AdWords API now supports TrueView campaigns that have migrated from AdWords for video, and several reports now include statistics and new metrics for these campaigns. See the release notes for the complete list of changes and additions.
  • New reporting columns for multi-channel advertisers are available on multiple reports making it easier to track interactions vs. clicks.
  • Customer Match. Build and target user lists from email addresses using the new CrmBasedUserList.
  • Structured snippets can now be created using extension setting services.
  • Conversion column changes. Conversion columns have been modified, added, or removed on multiple reports to coincide with the upcoming conversion reporting changes in AdWords. See the release notes for the complete list of changes.
  • HTML5 ads can now be added as TemplateAds using template ID 419. In addition, MediaService now supports uploading media bundles for use with this new template.
  • Geo targeted ad customizers. Target each ad customizer feed item to a specific geographic location.
  • Gmail sponsored promotions. The AdWords API now fully supports the Gmail image, single promotion, and multi-product ad formats via template ads.
  • Dynamic remarketing ads have new placeholder fields for setting upgraded URL attributes such as tracking templates, custom parameters, and final URLs.
  • Active View reporting. New fields for Active View viewable impressions, measurable impressions, measurable cost, and measurability are now available in multiple reports.

If you’re using v201502 of the AdWords API, please note that it’s being sunset on November 12th, 2015. We encourage you to skip v201506 and migrate straight to v201509. If you’re using v201506, be aware it’s now marked deprecated and will be sunset on April 11th, 2016.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201509 migration guide. The updated client libraries and code examples will be published shortly. With this release, we’ve also updated the Required Minimum Functionality document to include some of the newly added features. If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page.