Since our last
announcement in July, we've made several updates to improve the performance of the Google Ads API. Your feedback was essential to us in making these improvements and will continue to be throughout the remainder of the Beta.
What has been fixed?
Over the past several months, we've rolled out performance improvements to Google Ads API read and mutate functionality. Some of these updates are visible in recent versions of the API, such as the launch of
GoogleAdsService.SearchStream() in v3_0, while other improvements have sped up the response times of existing services and methods.
What's next for the Google Ads API Beta?
It is our top priority to get the Google Ads API ready for general availability. This involves rolling out features for key user journeys, for example: a service for asynchronous batch updates. If you have any feedback on the API's readiness to address your tool's requirements, we'd like to hear from you!
Which API should I use?
Throughout the remainder of the Beta, the
AdWords API will continue to be the primary API for programmatically accessing and managing Google Ads campaigns. When deciding whether to use the Google Ads API Beta to run production systems, please keep in mind that we may release updates in preparation for general availability. As a reminder, changes will be released in new
versions of the Google Ads API Beta. They will not affect your existing code unless announced otherwise on this blog.
If you have any feedback or questions regarding the performance, feature availability and overall usability of the Google Ads API Beta, please contact us at
googleadsapi-support@google.com.
-- The Google Ads API team
