Tag Archives: release

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

Today we're releasing v2.7 of the DCM/DFA Reporting and Trafficking API. This release introduces a number of video trafficking workflow enhancements, including:

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.6, which will sunset on May 31st, 2017. After this date, any requests made against v2.6 will begin returning errors.

As a final reminder, API v2.4 will be sunset on November 30th, 2016. To avoid an interruption in service, all users are required to migrate off of this version 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 v201609 of the AdWords API

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

If you’re using v201603 or v201605 of the AdWords API, please note that they’re now deprecated and will be sunset on October 25, 2016 and February 28, 2017, respectively. We encourage you to skip v201607 and migrate straight to v201609.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201609 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.6 of the DCM/DFA Reporting and Trafficking API

Today we're releasing v2.6 of the DCM/DFA Reporting and Trafficking API. This release includes a number of highly anticipated features, such as: We've also improved click-through URL management for Display creatives, expanded custom floodlight variable support, and much more. See our release notes for full details.

Retiring legacy creative types

Beginning with this release, the DCM API no longer supports creating legacy HTML5 Banner and Image creatives. As previously announced, these legacy types have been replaced by the new streamlined Display creative.

Additionally, the ability to upload Flash assets into DCM was disabled back in June. Accordingly, this functionality is also being removed from the API beginning with this release. Previous API versions will continue to support uploading Flash assets until their respective sunset dates, but users are strongly encouraged to begin transitioning to HTML5 now.

Deprecation and sunset reminder

In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v2.5, which will sunset on February 28th, 2017. After this date, any requests made against v2.5 will begin returning errors.

As a reminder, API v2.3 will be sunset on August 31st, 2016. To avoid an interruption in service, all users are required to migrate off of this version 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 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.