Custom Dimension with action scope: number of visits missing or is wrong #19164
Labels
Bug
For errors / faults / flaws / inconsistencies etc.
c: Consistent Reports & Analytics UX
For bugs and features that make Analytics reporting UI behave more consistently.
c: Custom Dimensions
For issues related to the Custom Dimensions plugin.
c: Data Integrity & Accuracy
Milestone
The background of this issue is whether you can also determine the (unique) number of visitors in a custom dimension with the action scope.
The simple table report for a Custom dimension for actions does not show the visits value in this case.
However, but I saw that the vertical bar graph and pie charts offer me to show the unique visitors.
Exporting to Excel also shows me a column with "nb_visits" and "nb_uniq_visitors".
Expected Behavior
I would initially expect this (unique) visitor value to be available in the simple reporting table as well.
And second, I would expect this value to be correct, which it is not.
Current Behavior
The unique visits value in the graphical charts and Excel export is incorrect as I found. The value is too high.
If I open the visits log from the simple table for a custom dimension with the action scope and count the visit entries (e.g. by exporting all entries to Excel), there are much fewer visits.
Steps to Reproduce (for Bugs)
Go to demo cloud:
https://demo.matomo.cloud/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?period=day&date=yesterday&idSite=1&category=General_Actions&subcategory=customdimension2
Select Author "Julien" and open visits log. Finally export all entries to TSV (it's in this case the method to count all visits).
I get 1.100 entries as visits in the export file.
On the other hand, if I use the pie chart, I get 1.247 visits for "Julien".
I guess I have a misunderstanding here in the concept of visits. But it should either show correct values for visits or none at all, neither in the export nor in the graphical charts.
Your Environment
The text was updated successfully, but these errors were encountered: