A very common forums support request is when users don't see any data in their report. We have extensive documentation about the many causes for no data..
A subset of these users actually successfully track the data (and can see it in the Visitor log) but they see "There is no data for this report" in all reports. And the likely cause of this problem is that the
core:archive task is not working. (Refers to the 3rd bullet point in our FAQ
Archiving triggered from the browser must be enabled, if it is disabled the Cron script must be configured properly)
So the idea is to help these users and put them on the path to resolving the issue.
core:archiveconsole command, and that you have configured a
MAILTOto receive errors by email if the archiving fails. You can also try to run the console command to archive your reports manually: \n ./path/to/matomo/console core:archive --url=http://example.org/piwik/" ( ideally we replace the URL automatically by the URL and maybe the path)
When we write "There is no data for this report" and detect that archiving hasn't been successful in a while, then
we could guide users to setup the cron archiving for an optimal user experience. this would ultimately make Matomo much faster and would reduce amount of users who experience a slow Matomo (many people say Matomo is slow because browser archiving runs and is slow).
For example, if users don't have yet disabled the "Browser archiving trigger" feature:
Aren't we already notifying users by email when this happens?
We are not emailing them except the crontab may email then the error if they have the crontab setup correctly, but most of the time they don't have the crontab setup.
I see... I realise this was on cloud, not in core.