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
met
Many of the deprecated fields can be derived from other fields but two in
particular cannot:
- conversionsManyPerClick [display name = Conv. (many-per-click)]
- totalConvValue [display name = Total conv. value]
Does anyone have insight into why there two fields have been removed from
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 reaso
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 yo
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.
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
w
