@guywillett opened this Issue on March 27th 2020

Currently, viewing Unique Visitors on the Visitors Map is only possible when the "day" period is selected.
Screen Shot 2020-03-27 at 07 46 29
If any other period (in this example, a week)is applied then unique visits is no longer an option to be displayed:
Screen Shot 2020-03-27 at 07 47 02
I think this should at least be configurable, and probably respect the config as described here https://matomo.org/faq/how-to/faq_113/
Screen Shot 2020-03-27 at 07 53 07

For completeness we are using Matomo v3.13.1

@tsteur commented on March 29th 2020 Member

Good point @guywillett

@tsteur commented on March 29th 2020 Member

Thanks for creating the issue 👍

@sgiehl commented on March 30th 2020 Member

I guess the reason is, that we are actually not calculating the exact unique visitors for the location reports. For periods bigger than day, there is only the sum of unique daily visitors, which is not the same. Not sure if we should show that as unique visitors 🤔

@guywillett commented on March 30th 2020

For periods bigger than day, there is only the sum of unique daily visitors, which is not the same

If I understand correctly, you mean the same "unique visitor" may visit on different days in the period and therefore should only count once for the period? In which case, I see what you mean - a bit tricky!

But is this not the same conundrum that has been solved and implemented in other parts of matomo that do show unique visits for different time periods? (and is configured by enble_processing_unique_vistors_PERIOD).

@sgiehl commented on March 31st 2020 Member

Right, we do that processing for some other reports. But that means we can't (only) simply combine the reports already generated for day period, but would need to completely process all raw log data for the bigger periods. Depending on the amount of data tracked, that can be quite a resource killer...

@guywillett commented on March 31st 2020

BTW thanks for the attention and replies to this issue :-)

Yes, I understand that it can be quite a resource killer and may take a long time - but perhaps that is why it should be configurable and users opt-in to it.

Powered by GitHub Issue Mirror