Danial, thanks for the reply, I've worked with the AdWords API since v13 so I'm well aware of all of these things already. I'm sorry to say that the only things that Google could do to improve my experience when it comes to the API would be to release new versions less frequently, and when new versions need to be released that greater care be taken with backwards compatibility.
I would be more ok with taking time to update if I ever wanted to use new features that were added, but I spend hours every time a new API version is released just making sure what I do currently still works, and finding workarounds for removed functionality. There is little or no benefit to the end user to the breakneck speed of API releases. I've had a far more pleasant experience with the MSN/Bing adcenter product, which works just as well and releases new API versions every few years. This is more than sufficient to my needs. I'm realistic about the fact that this feedback will never be taken into consideration, but just wanted to make sure it was heard. Steve On Wednesday, July 17, 2013 4:20:13 AM UTC-4, Danial Klimkin wrote: > > Hello Steve, > > > Thank you for your feedback. We realize each API migration requires you to > update your client applications. We took several actions during the last > year to improve your experience, while tried to balance changes to the API > with new AdWords feature launches for our developers: > > > - > > To help with migration, we’ve put a release > schedule<http://googleadsdeveloper.blogspot.com/2012/08/release-schedule-for-adwords-api.html>in > place. With the schedule, we limit the number of major releases to three > per year and ship them on the dates you know in advance. Along with a > clear sunset > schedule <https://developers.google.com/adwords/api/docs/sunset-dates>, > this should allow to plan your time to be prepared. > - > > We’ve improved our documentation and compiled a migration > guide<https://developers.google.com/adwords/api/docs/guides/migration-v201306>for > each version change. These migration guides outline all changes > required to upgrade to a newer version making the process simpler. > - > > Our client > libraries<https://developers.google.com/adwords/api/docs/clientlibraries>available > for all major programming languages are now shipped on the same > day as the API release. We also provide additional utilities for the API, > such as authorization and reports download. In many cases, API version > change requires to change only one constant in the code. > > > We hope these resources are useful to you and simplify the migration > process as much possible. > > -Danial, AdWords API Team. > > > On Thursday, July 11, 2013 9:48:12 PM UTC+4, Steve Wollkind wrote: >> >> I was in the room at the NYC adwords api seminar when this was discussed >> at length so I know I'm not alone and I know this sentiment isn't new, but >> I just want to take this moment to once again complain about the ridiculous >> pace of API changes and sunsets. No other API I've ever worked with has >> forced me to spend as much time running in place to keep up with changes as >> the Google Adwords API does. >> >> I'm sure Google feels that there is a benefit to this, and perhaps for >> Google there is, but it makes developing a huge pain, and never do I want >> the new "features" that are added. I just want what I've already got to >> keep working. More often than not you remove functionality I use. >> >> I'm sure you are pleased to announce this release. I'm certainly not >> pleased to hear about it. >> >> Steve >> >> >> On Wednesday, July 10, 2013 5:24:54 PM UTC-4, Danial Klimkin wrote: >>> >>> 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<https://developers.google.com/adwords/api/docs/reference/> >>> . >>> >>> *v201306 Highlights:* >>> >>> - *Three additional reports are now available to all API users.* >>> Campaign >>> Ad Schedule >>> Target<https://developers.google.com/adwords/api/docs/appendix/reports#campaign-ad-schedule-target>, >>> >>> Campaign Platform >>> Target<https://developers.google.com/adwords/api/docs/appendix/reports#campaign-platform-target>and >>> Display >>> Keyword Performance >>> reports<https://developers.google.com/adwords/api/docs/appendix/reports#display-keyword> >>> . >>> - *Additional targeting options for Feeds.* >>> Feeds<https://developers.google.com/adwords/api/docs/guides/feed-services>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<https://developers.google.com/adwords/api/docs/reference/latest/CustomerSyncService>now >>> returns all changes related to the Feed services. >>> - *MutateJobService now supports Feed and AdGroupBidModifier >>> operations.* You can now use >>> MutateJobService<https://developers.google.com/adwords/api/docs/reference/latest/MutateJobService>to >>> update Feeds and AdGroupBidModifiers asynchronously. >>> >>> >>> If you are still using v201209, please note that it is being >>> sunset<https://developers.google.com/adwords/api/docs/sunset-dates>on July >>> 22, 2013. We encourage you to skip v201302 and migrate straight to >>> v201306. Follow the Ads Developers Plus >>> Page<https://plus.google.com/+GoogleAdsDevelopers>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<https://developers.google.com/adwords/api/docs/reference/>and the >>> v201306 >>> migration >>> guide<http://developers.google.com/adwords/api/docs/guides/migration-v201306>. >>> >>> We have also published updated client >>> libraries<https://developers.google.com/adwords/api/docs/clientlibraries>with >>> code examples. If you have any questions or need help with migration, >>> please post on the >>> forum<https://developers.google.com/adwords/api/community/>or Ads >>> Developers Plus Page <https://plus.google.com/+GoogleAdsDevelopers>. >>> >>> - The AdWords API Team >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
