New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing performance metrics for most dates #17761
Comments
@mikkeschiren for days that have missing metrics, can you check in the log_link_visit_action table if there are any positive values in the performance dimension columns, for example |
@diosmosis - values were in fact NULL on the dates with no data that I tested, how could this happen? |
@mikkeschiren are you using the normal javascript tracking? Those values should actually be automatically tracked in this case (if the users browser provides them). |
I will check with our analysts if they have done some changes on some dates, but with the results we are getting, that does not really make sense (couple of days per month that we have results, and then thousands of them, and next day none). But with that said - it could be an implementation problem. |
@sgiehl wouldn't it be expected in some cases when the tracking request is sent before the browser load event for example and there is no follow up load event? |
Yes. indeed. If the page tracking event is sent before the performance metrics are available they will be sent with the next tracking request. If no further tracking request is sent, the performance metrics might not be tracked at all. |
This could be a implementation issue, I think we can close this now. |
👍 thanks for letting us know @mikkeschiren |
When viewing the performance metrics we are missing data for most dates
Expected Behavior
When looking at performance metrics we expect to find data for all dates.
Current Behavior
We have data for different dates.
We are using Matomo 4.3.1
Data is archived with cron archiver, no errors in the logs for missing dates for performance metrics.
The text was updated successfully, but these errors were encountered: