Yes, I completely agree with this! Adwords API has been very robust and stable since past many years and the new version is definitely one of the bad and worst (As per my my experience). The whole migration is not so easy, it would take so many months of work to map the old functions of Adwords API with the new Google Ads API.Plus I also feel the new version of API is slower and also poor API documentation and lacks some advanced code examples. And Finally I am surprised to know that Reporting CSV Download feature is removed, I am sure Reporting is the base and most used feature for most of the Tech companies and Downloading CSV and import data in database is very fast (Specially for big accounts) using old Adwords API, but with the new one its damn slower. For Example Lets say there is an Account with more than 5K Campaigns and we need to download the Campaign Performance Report, then from old Adwords API we easily import data from CSV, but now through new one since CSV Download is removed we need to iterate over each data which makes performance slower.
On Sunday, June 16, 2019 at 4:07:48 AM UTC+5:30, PPC Developer wrote: > > Hi, > > We've been building on top of AdWords API for 5 years now. Our integration > has gone through solid time of stress testing and have a very stable server > code base now. AdWords API has been very stable lately, as it's around 10 > years old. This new Google Ads API is a massive undertaking, and I'm trying > to understand what really is the benefit here? I read that it's using a > different protocol and is strong typed, but the current API is working just > fine. > > This whole migration will cost us so many man-months of coding and testing > and stabilization afterwards. I would imageine hundreds of millions of > dollars worth of pain and agony we have to go through collectively > (globally, all Google API customers). And what do we exactly gain? > > 1- There are no new scenarios or functionality enabled with the new APIs, > am I missing something? > 2- Some concepts and API services do not exist in new API, such > as AdCustomizerFeedService, which seems that the new API is not fully ready > yet. > 3- There's a note about how the new gRPC protocol is implemented more > efficiently than SOAP/XML. Well, the web as we know today is completely > fine using SOAP/XML. Google's current APIs are running very well and fast. > So what is exactly gained by switching to an entirely new protocol? > > For us to fully migrate and stabilize the new code base, it will > definitely take over 1 year of effort. I'm guessing there's more customers > out there who share similar views. > > My question here for Google is : Why not keep supporting the previous > AdWords API and keep publishing new versions? Looks like you guys changed > the object model to be more in tune with the new AdWords UI. But why does > that force you to stop supporting the AdWords API? Looks like both APIs > have been tested to work side by side, so looks like a lot of work has been > done from your end to support AdWords API in parallel with the new API. > > I'm trying to understand the rationale behind this massively costly > industry-wide move, where it seems that there's no benefit or gain to us. > Please help us understand how this new API is worth spending hundreds of > millions of dollars from your partners point of view. > > > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/c066b41c-a9b5-45a5-a092-2bf7474b0acb%40googlegroups.com.
