Hi,
Starting yesterday we have started to see the RATE_EXCEEDED error a lot for
the Traffic Estimator Service... we have been using this service for months
with roughly the same workload with very few exceptions but for some reason
we have started getting more and more exceptions.
RateName = R
OK Thanks. Is this likely to change before the 11 April when v201506 is
depreciated?
Currently we can get data for all the conversion types in one report but
unless this is fixed in 201509 or 201601 (or the next version of the api)
then we need to find a different way of getting the conversion
Has there been any update on this? We have the same problem (it works fine
in v201506 but not in v201509 or v201601).
On Wednesday, March 2, 2016 at 8:52:52 PM UTC, GregT wrote:
>
> Hi,
>
> In v201509, the shopping performance report got columns added to allow
> segmentation by conversion typ
