@utrautmann opened this Issue on May 2nd 2022

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".

grafik
grafik

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).
grafik

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".
grafik

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

@bx80 commented on May 8th 2022 Contributor

Hi @utrautmann, thanks for the detailed report.

I've worked through those steps to try to recreate the issue using the same date as your example on demo2. (https://demo.matomo.cloud/index.php?module=CoreHome&action=index&idSite=1&period=day&date=2022-05-01#?period=day&date=2022-05-01&idSite=1&category=General_Actions&subcategory=customdimension2)

The page authors listing shows 1,519 actions and 1,263 unique actions.

In the export file I get 1519 hits and 1,263 visits. I didn't see the 1,100 entries as visits, if you can still see this value could you provide a screenshot?

image

The pie chart is showing 1,247 unique visitors.

Unless I'm misunderstanding the issue, all these value look correct.

There were 1,247 people who visited Julien's pages (nb_uniq_visitors), some of these people made multiple visits (same visitor returning >30mins since the last visit) so there were 1,263 visits (nb_visits). During all these visits Julien's pages were viewed 1,519 times (nb_hits).

How visit is defined
How unique visitors are counted
What is a hit in Matomo

I hope that's helpful.

@utrautmann commented on May 13th 2022

Hello @bx80 , thanks for your explanations.

I think there is really a misunderstanding between us.

You exported the custom dimension values to see the number of visitors.
However, I selected the visitor log for a specific value ("Julien") from the custom dimensions and counted the entries there with an export. And this is where I see differences.
grafik

The visitor log has fewer visits than the export from the custom dimensions (when I compare it to nb_uniq_visitors).
grafik

To the background:
I noticed this when I created a new custom dimension (scope action) in another project and it was actually only 2 unique visits according to the visitor log that triggered a specific action value in this custom dimension.
Although these had triggered the relevant action several times, there were only two unique visits.

However, the custom dimension export and pie graphic showed me 4 nb_uniq_visitors.

And so I went in search of whether there were any differences in the demo platform. And they were.

@bx80 commented on May 16th 2022 Contributor

Thanks for explaining this in more detail @utrautmann, my mistake I was looking in the wrong place. The nb_uniq_visitors for the custom dimension should be matching the number of rows in the exported visitor log for the segment. I'll mark this as a bug so our product team can prioritize it. :+1:

Powered by GitHub Issue Mirror