@Situphen thank you for reporting this, our product will review this.

@peterhashair it'd be good to confirm we can reproduce this issue and check it's not a regression.

@Situphen trying to reproduce this, but it seems like it works on my local. I notice your label param is tutoriels+>+3645+>+demontrer-par-labsurde, and the actual response label is demontrer-par-labsurde. Can you try a request with label=demontrer-par-labsurde

I tried a request with label=demontrer-par-labsurde as you suggested and I got an empty response : {"2022-06-28":[],"2022-06-29":[],"2022-06-30":[],"2022-07-01":[],"2022-07-02":[]} with period=day and [] with period=range.

@Situphen how about without label, and do a search on-page (ctrl+f) for demontrer maybe, just to confirm what the actual label is in the response, it could be caused by special characters.

With period=day

Request parameters without label=... but with expanded=1:

/index.php?module=API&format=JSON&idSite=6&period=day&date=2022-06-28,2022-07-02&method=Actions.getPageUrls&expanded=1

Correct response (3 responses with the label demontrer-par-labsurde as before and 2 with the label /demontrer-par-labsurde.pdf when filtering with demontrer in Firefox) :

With period=range

Request parameters without label=... but with expanded=1:

/index.php?module=API&format=JSON&idSite=6&period=range&date=2022-06-28,2022-07-02&method=Actions.getPageUrls&expanded=1

Incorrect response (nothing when filtering with demontrer in Firefox):

@Situphen thanks for providing this, I will do more investigation on this

As you were not able to reproduce this behavior, I investigated further and for some date range it works and for some other it doesn't. So I downloaded the data with period=day with a date range of 30 days (filename data_day_*.json) as well as the data with period=range for all possible date range combinaison (filename data_range_*.json) with a Python script (get_data_range.py). For each date range combinaison, I compared the nb_visits result I got from period=range to the sum of each daily nb_visits with another Python script (analysis.py). I sorted the date ranges in two lists: correct and incorrect (filename analysis_*.json). Everything is inside this zipfile below. I was not able to find a strict pattern common to all incorrect date ranges, but maybe you will be able to?

test-matomo.zip

@Situphen thank you very much for providing the additional info and scripts, it really helps, I will come back to you ASAP.

@Situphen I haven't had a look in detail, but that might be an issue of data truncation. When reports are archived, the aggregated data is limited to a certain amount of records. For actions the default is 500 for the base report and 100 for all subtables. Depending on the amount of page you are tracking it might happen that pages that are visited quite few are summarized into a Others row. So in theory a page can be visible on each day report, but if each day has varying pages tracked, a bigger period (e.g. week, month, year or range) might not contain a certain row as the report would have too many records.