Google Ads Developer Blog: adwords_api

Ads Developer Blog

The official blog for information about the Google Ads, Google Ad Manager, Google Mobile Ads SDKs for AdMob and IMA SDKs, and other Google Advertising Platform developer tools.

Reminder: AdWords API v201306 and Ad Exchange Buyer SOAP API v201306 to be sunset on March 31

Thursday, March 13, 2014

As we have previously announced, if you're using the AdWords API or Ad Exchange Buyer SOAP API v201306, please note that support for this version will end on March 31st, 2014. If you are still using v201306 after that date, all requests will fail and your application will cease working until you migrate to a supported version. You can reference either the v201309 or v201402 migration guides for help upgrading to one of these versions.

In addition, remember that ClientLogin support is deprecated and you will have to migrate to OAuth 2.0 in order to authenticate starting in version v201402. It may be best to get this out of the way now, because with the sunset of v201309 on July 21st, 2014, all support for ClientLogin will go away and OAuth 2.0 will be required to access the API. Please reference our OAuth 2.0 migration guide for help with this process.

If you have any questions about this upcoming change or anything else related to the AdWords API, please contact us on the forum or via our Google+ page.

- Michael Cloonan, AdWords API Team

Google

Labels: adwords_api , adwords_api_v201306 , sunset

AdWords API: Upgrading your Ad Extensions - a reminder

Friday, August 16, 2013

As previously announced, starting on September 23, 2013, call, app and sitelink extensions will automatically upgrade to their new formats. If you haven’t done so already, we encourage you to upgrade your extensions ahead of the September 23 deadline so you can take early advantage of the new features, accrue statistics on the upgraded extensions sooner, and ensure that your extensions continue to show.

Starting on the upgrade date, the following changes will take place:

You won’t be able to use CampaignAdExtensionService.mutate to update your legacy extensions.
The 25 characters limit will take effect. Make sure you adjust your sitelink text to 25 characters or less so your extensions continue to show.

The use of CampaignAdExtensionService.get for legacy call, app and sitelink extensions, will be available through October 23. You can use it to consult and compare your legacy extensions data with their upgraded counterparts.

If you allow your legacy extensions be auto-upgraded, the system will do its best to detect and avoid creating duplicate extensions. We recommend that you check all your extensions after the upgrade is finished to ensure they’re configured as you’d like.

Resources
To learn more about managing upgraded extensions with the AdWords API, make sure to consult the Feed Services guide. For a code example on how to upgrade extensions on your own, look in the migration folder in all client libraries.

If you have questions or need help with the upgrade, please visit us on the developer forum or the G+ page.

- David Torres, AdWords API Team

Google

Labels: ad_extensions , adwords_api , adwords_api_v201306 , enhanced_campaigns , sitelinks

Announcing v201306 of AdWords API

Wednesday, July 10, 2013

We are pleased to announce the release of AdWords API v201306. This latest release introduces new reports, adds platform targeting options for the Feed services, and includes improvements across other services. A complete list of changes is available in the release notes.

v201306 Highlights:

Three additional reports are now available to all API users. Campaign Ad Schedule Target, Campaign Platform Target and Display Keyword Performance reports.
Additional targeting options for Feeds. Feeds can now be targeted specifically to Mobile or Desktop platforms. Beta users can also try out AdSchedule targeting for Feeds which allows you to specify certain hours or days of the week for the extension to show on.
CustomerSyncService improvements related to Feed services. CustomerSyncService now returns all changes related to the Feed services.
MutateJobService now supports Feed and AdGroupBidModifier operations. You can now use MutateJobService to update Feeds and AdGroupBidModifiers asynchronously.

If you are still using v201209, please note that it is being sunset on July 22, 2013. We encourage you to skip v201302 and migrate straight to v201306. Follow the Ads Developers Plus Page for tips and tricks about migration. If you’re using v201302, be aware it is now marked deprecated and will be sunset on November 8th, 2013.

As with every new version of the AdWords API, we encourage you to carefully review all changes in the release notes and the v201306 migration guide. We have also published updated client libraries with code examples. If you have any questions or need help with migration, please post on the forum or Ads Developers Plus Page.

- The AdWords API Team