Missing default for top parameter on elements leads to "data loss"

[sdoering]

Hi @dancingcactus,

having done some analyses in the past weeks I stumbled upon a strange behavior, when querying variables with different metrics (be it instances, visits, pageviews or custom events). Doing requests spanning multiple months I got differing numbers then receiving in the adobe frontend. Esp. if I was doing breakdowns with multiple variables.

After some digging I stumbled upon the Adobe product forum encountering others with the same issue.

Some more digging brought a solution. There is a parameter one can add to the elements method to ensure more then (currently 10) rows of results being delivered from the API. Currently no one seems to know why Adobe has such a low default value of 10 for this parameter.

Here an example code to fix the problem:

segment = 'sXXX_SSSSXXXXXXXXXXXXX'

backend_data = suite.report.elements('propXX', top=500) \
.elements('evarXX', classification = 'Name', top=250) \
.elements('evarXX', top=250) \
.metric('instances') \
.filter(segment) \
.range('2017-01-01', stop='2017-12-31') \
.granularity('month') \
.run()

Maybe the python omniture module could implement a default that is a little bit more sane, then the currently implemented Adobe one.

Thanks a lot for the great piece of software.
Sven

[jrjames83]

Thanks - just saved me an enormous headache!