Tag Archives: release

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

Today we are releasing v2.2 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:
  • User requested enhancements: You asked and we listened! Based on your feedback, new fields--such as computed click-through URL for ad creative assignments--have been added.
  • Placement search improvements: You can now search for placements and placement groups by start and end date.
  • Ins tag support: When the new ins tag is enabled for your account, requests for iframe and javascript tags will return an updated tag format. We've introduced 4 new legacy tag values you can use to access the older versions of these tags, to ensure a smooth transition to the upgraded format. You can begin requesting these legacy tag values today, even if your account hasn't upgraded yet.
Retiring older API versions

Along with this release, we're introducing a new deprecation schedule and announcing the deprecation of all versions prior to v2.1. Moving forward, we will generally only support 3 versions of the API and sunset the oldest version 4 months after a new release. In order to help developers adjust to this new schedule, we're providing an extended migration period for users of these newly deprecated versions:

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

These versions will remain active and supported until the sunset date, and we encourage you to use this time to update your applications.

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!

 - , DCM API Team

Announcing v201506 of the AdWords API

Today we're announcing the release of AdWords API v201506. Here are the highlights:
  • Location extensions within a geographic area is now configurable through the API, which in previous versions was a read-only feature. LocationGroups provides a feedIdthat is now required when specifying a LocationExtensionOperand in the matching function.
  • Updates to reporting. Gmail Sponsored Promotion stats are now available in reporting. We’ve added new columns to existing reports, including the Final Url column to the Search Query report and start and end dates to Campaign Performance report. See the release notes for the complete list.
  • Improved ConstantDataService. CriterionUserInterest objects now have a new parent ID attribute that allows for navigation of the user interest taxonomy hierarchy.
  • AWQL improvements. You can now explicitly include or exclude zero impression rows when requesting reports using AWQL. Also, the DURING clause became optional when defining ALL_TIME reports. Shared set services were extended with the AWQL query() method. 
  • Improvement to labels. You can now programmatically set label descriptions and colors using the API.
If you're using v201409 of the AdWords API, please note that it's being sunset on July 28th, 2015. We encourage you to skip v201502 and migrate straight to v201506. If you're using v201502, be aware it's now marked deprecated and will be sunset on November 5th, 2015.

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

Announcing v201502 of the AdWords API

Today we're announcing the release of AdWords API v201502. Here are the highlights:
  • Ad extension services. We heard your feedback about Feed Services being overly complex for many cases. To help simplify ad extension management, we've added new ExtensionSetting services. Existing Feed Services are still supported so you can continue using them. Should you decide to migrate to the new services, we've prepared a migration guide.
  • Account labels. We've expanded support for labels to MCC manager accounts. Now you can tag your accounts with text labels programmatically.
  • In-place URL upgrade for ads. The AdGroupAdService now supports upgradeUrl method which simplifies the Upgraded URLs migration.
  • Updates to reporting. Two new reports have been added: UserAdDistance performance and Label. Reporting now supports skipColumnHeader HTTP header which removes column headers from the produced report. We've also added several new columns across reports, see the release notes for the full list.
  • Shared sets. These are now available to all AdWords API users. Check out this feature if you often need to attach large sets of negative keywords or placements to many campaigns.
  • Support for application deep links. You can now create ads linking to specific activities in your application using AppUrlList.
  • Additional controls on Local Inventory Ads. You can now enable local inventory as well as set product channel / channel exclusivity.
  • Cross-account as well as system-defined conversion trackers are now easy to identify. Look at the conversionTypeOwnerCustomerId in ConversionTracker. Accounts using cross-account conversion tracking can be identified using the effectiveConversionTrackingId.
  • Account-level remarketing tags can now be retrieved using CustomerService RemarketingSettings.
  • The new TargetOutrankShare bidding strategy is now supported.

If you're still using v201406 of the AdWords API, please note that it's being sunset on April 6th, 2015. We encourage you to skip v201409 and migrate straight to v201502. If you're using v201409, be aware it's now marked deprecated and will be sunset on July 14th, 2015.

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

 - , on behalf of AdWords API Team.

Announcing v201409 of the AdWords API

Today we're announcing the release of AdWords API v201409. Here are the highlights:
  • Mobile campaigns for search and display. Search Mobile App and Display Mobile App campaign subtypes are now available via CampaignService. These new subtypes are a simplified way of creating campaigns focused on mobile app promotion.
  • Ad Customizers. Ad Customizers previously available for Test Accounts only are now enabled in production. With this feature you can include dynamic values in your ads based on feed data.
  • Currency support for conversions. Conversion trackers (including offline conversions) now support currency specification. You can also set default currency per tracker.
  • Website call conversion tracker. This tracker allows the collection of conversion stats for calls made on a script-generated phone number placed on your website.
  • Rule-based remarketing lists. The new API version allows you to create and manage rule-based remarketing lists. This feature allows you to use simple rules to better target the people who visited your website.
  • Better Labels handling. LabelIds column is now available in all relevant reports. We've also added both Labels and LabelIds columns to the Criteria Performance report.
  • Updates to reporting. A new Extension Placeholder report is now available for retrieving consistent extension stats. Reporting interface was extended to allow you to control the presence of report headers and footers in the response.
There's also an important API-level change in v201409. Starting this version, the clientCustomerId header is now a required header for calls to all services except CustomerService. If your application relies on a default account identified by authorization credentials, you need to update it to send a valid customer ID for every request. You can obtain the customer ID via a get call to the CustomerService.

If you're still using v201402 of the AdWords API, please note that it's being sunset on November 6th, 2014. We encourage you to skip v201406 and migrate straight to v201409. If you're using v201406, be aware it's now marked deprecated and will be sunset on April 6th, 2015.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201409 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 that are now required in third-party tools. If you have any questions or need help with migration, please post on the forum or the Ads Developers Plus Page.

 - , on behalf of AdWords API Team.