I don't consider it wasting Google's resources when I'm paying for API tokens. :) There's also a certain degree of comfort in knowing that the calculations made by Google will be consistent with what is shown in the principle AdWords interface. As srohde mentions below, not having those two metrics is particularly troublesome. And while I have large sections of code that rely on AdHoc reports, you still cannot sort that data on the initial request, creating more technical overhead for us to even contemplate offering that (sorting a 20,000 keyword SQP reports by three metrics is not fun, and shouldn't be done on our end).
If Google offered sorting the AdHoc reports (even through their new AWQL feature), I would have zero complaints about the Stats being deprecated (I'd probably stop referencing it altogether). - Stephen On Monday, July 23, 2012 3:45:36 AM UTC-5, Zweitze wrote: > > Oliver, > > When you request the calculated data from Google servers, you are not only > wasting Google resources but also network resources (you are downloading > data that you can calculate) and processing resources (you are > uncompressing data that you can calculate with less effort). > For that reason we decided to leave calculated data as is and do the > calculations ourselves. Although it was an 'old-days' decision when report > downloads were limited to 256 MB. > > Regards > > > On Thursday, July 12, 2012 5:28:34 PM UTC+2, Oliver wrote: > >> >> zweitze, we found out these fields will be deprecated in the object >> services and not in the reports. What a relief. >> >> We can do what you suggest, but why waste our server resources and slow >> down our users when this data is readily available in the reports? I know >> you will need to do this if you need to work out a custom date figure from >> within your local copy of the data, but for daily data we prefer to grab >> and trust the API's. >> >> >> On Thursday, July 12, 2012 1:02:17 PM UTC+1, Zweitze wrote: >>> >>> I never request such fields in adhoc reports but instead calculate them >>> from other results. For example: >>> 1. Instead of requesting CTR calculate Clicks/Impressions >>> 2. Instead of requesting ConversionRate calculate Conversions/Clicks >>> etc.etc. >>> >>> Most of them are divisions so beware of divisions by 0. Also beware of >>> ViewThroughConversions which can lead to conversion rates higher than 100%. >>> >>> Hope this helps. >>> >>> >>> >>> On Monday, July 9, 2012 8:46:42 PM UTC+2, Oliver wrote: >>> >>>> In the release notes of v201206: >>>> https://developers.google.com/adwords/api/docs/reference/#v201206 >>>> >>>> it says some stats fields have been removed inlcuding commonly used >>>> fields like conversionRate, costPerConversion, etc. >>>> >>>> I can still see these fields in the reports types which got updated >>>> only a week ago: >>>> https://developers.google.com/adwords/api/docs/appendix/reports >>>> >>>> Can you please confirm if these fields will be removed from the adhoc >>>> reports? and if so, how else can one get these performance fields? >>>> >>>> Thanks >>>> >>>> Oliver >>>> >>> -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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
