Thanks Oliver, Greg.
Oliver's example demonstrated all the fields being rounded and has been
communicated to the core engineering team. Waiting to hear back from them.
- Kevin Winter
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwo
Hi, Kevin.
I've emailed you an example with this information. Except I just noticed
you asked explicitly for ValuePerConv and ValuePerConvManyPerClick -- our
reports don't include those so I just realized what I sent might not be what
you were looking for. What I sent was an example of the To
Hi Kevin,
thanks for the context about the status quo. I got a report here and will
mail it in a minute.
Best regards,
Oliver
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords
Hi Greg, Oliver,
Any chance you could email me a customerId and reportDefinitionId (and
possibly the downloaded report) where ValuePerConv and/or
ValuePerConvManyPerClick
are being returned back with a single decimal place? Email: Kevin.Winter @
google.com
- Kevin Winter
--
=~=~=~=~=~=~=~=
Hi Greg, Oliver,
I'd like to provide a little context for why it is returning a rounded
number and why it was not originally made a Money field.
When conversions were built, it was intended that the conversion value could
represent other items aside from currency. For example, see this
docum
Hello all.
Thanks Greg for bringing this issue up and to our attention. We, too, stand
shortly before migrating from v13 reports to the latest
ReportDefinitionService API and rely (in part) on conversion values
transmitted through the API.
The issue of rounded conversion values in the keyword/
Hi, Keven.
Thanks for responding.
As for whether or not the UI behavior matches the API, I guess the answer is
yes, although it makes it harder for us to match the UI. :) The conversion
values for the individual keywords and ad groups are indeed shown as rounded
in the UI in the same way as
Hi Greg,
The v201101 version of reports addressed a number of shortcomings of the
old v13 reports. As a result, some of the behavior may be different.
Regarding bugs, we recommend comparing the UI report behavior to the API
report behavior - if the two do not agree, we should either have it
Hi.
We're trying to transition some reports we run from the V13 API to the
v201101 API. Something we're seeing is that the conversion value that we
are getting from the v201101 Keyword Performance and Search Query
Performance reports appears to being rounded to the nearest tenth of a
"dollar"