First, thanks for providing the segments API-- lots of great
functionality that have made my life a lot easier. One remaining
challenge on my end is parsing the return when I request the definition
field, particularly when a segment uses a time-within operator. I
noticed that the API seems to now handle within operators, but still
fails for after. For the latter, I still receive definition of:failed
converting segment definition: failed converting restriction idThis is
in contrast to within, whe...
Yep, you just make a simple CM using row count and use that to make your
request to get the top value. Note that you will need to include at
least one non-calc metric, e.g. visits to actually pull any data. Also
note that to get the expected result, you can only have a single
breakdown, as you want to get the row count for the single breakdown
dimension. This means that you want a report that does not have a date
breakdown built-in. I just use a Ranked report. Re: overlapping data: I
Yes, that's the default; the library I use to access the API strings
together Report.Queue() and Report.Get() into a single function, and
provides the option to use the "default" workflow with the enqueueOnly
argument. Sorry for not making this clear. Pretty much. Informally, I've
noticed between 2-6x improvement in throughput, depending on the nature
of the request. You can give yourself a bit of ceiling in your initial
top value. I often make a call to determine the number of rows using the
Thanks, ChrisS_ws; worked with a tweak to the function name, i.e.URL =
cleared a bunch of reports that were clogging up the queue. Look forward
to the fix for 1.4, but in the meantime, I'll definitely take a working
1.3 version over nothing.
In our implementation, the server seems to process up to 8 queued
reports at a time. The queue seems to be in order of request receipt.
Say you have a baseline list of args, and that you know the 'top'
parameter ahead of time. Note the reporting API has a 50K limit for
'top.' List of 9 $ reportsuite.id : chr "myID" $ date.from : chr
"2016-09-01" $ date.to : chr "2016-09-02" $ elements : chr "my_element"
$ metrics : chr [1:2] "pageviews" "visits" $ segment.id : chr [1:2]
"segment1" "segment2" $ d...
I have reports in the queue that I'd like to clear. Previously, I could
accomplish this by calling the Report.Cancel method. For a few months
now, this has not worked, and I instead receive a response of:When
trying in the API Explorer, I receive a message of:This has been
reported by others, e.g.: Cancel Report Function returning with error
each time. · Issue #222 · randyzwitch/RSiteCatalyst · GitHub I'd
appreciate any insight/assistance.