@sandeepdixit2020 opened this Issue on May 5th 2020

API at Matomo Version 3.8.1 For which result changes after Matomo version upgrade.

/index.php?module=API&method=Events.getName&secondaryDimension=eventCategory &idSite=6&period=day&date=2020-04-23 &token_auth=XX&filter_limit=-1 &flat=1&segment=dimension6==2020DecorativeItemsUS2020

(at Matomo Version 3.8.1 Segment working as expected)

Upgrade to 3.13.2 (or 3.13.5) and invalidateArchivedReports for 2020-04-23

Above API now returns different results. We can see that data that is not from segment=dimension6==2020DecorativeItemsUS2020

Because all of our API segment by dimension6, it's a big issue for us.
API Results before after update, Screenshots ,visit logs attached. dimension6 is catalog code on Matomo UI.

please note that we created one environment, from backup of 3.8.1 just to verify this issue, as this is very critical problem for us.
We did not change any configuration in between on upgrades. We have been able to reproduce this scenario many times.

dimension6 is named catalogCode on Piwik UI.

API response before Update. Screent shot of UI report and API result as xml.

Event Names 3 8 1

API response after Update. Screent shot of UI report and API result as xml.


Event Names 3 132

Other important data to help debugging

VisitLog 1
VisitLog Part 2

VisitLog3_Showing DimentionValueToFilter

@tsteur commented on May 5th 2020 Member

Hi @sandeepdixit2020 this is due to https://github.com/matomo-org/matomo/issues/11900 and now expected behaviour change as it actually was buggy initially (I totally understand some users like you prefer and expect the other behaviour how it used to work, sorry about that). Here's a workaround: https://github.com/matomo-org/matomo/issues/15130#issuecomment-551252343

the feature you are likely looking for are "filters" and we have an issue for this here: https://github.com/matomo-org/matomo/issues/15438

This Issue was closed on May 5th 2020
Powered by GitHub Issue Mirror