Skip to content
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

Jump to bottom

Why are numbers of tracked visits changed retrospective? #19473

Open
ckrapp opened this issue Jul 6, 2022 · 2 comments
Open

Why are numbers of tracked visits changed retrospective? #19473

ckrapp opened this issue Jul 6, 2022 · 2 comments
Labels
Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced.
Milestone
For Prioritization

Comments

@ckrapp
Copy link

ckrapp commented Jul 6, 2022

Hi. I usually check the numbers of tracked visits and pageviews once per month for the past month and note them in a separate list. When I did so in the beginning of June, I noticed that the numbers for April, March and February had changed retrospective, compared with the numbers I noted previously. Some increased, some decreased, the total was different for this period. Older numbers were consistent and did not change, neither did this problem reappear in July/June. Does anybody know, why this happened? Thanks for your help!
@ckrapp ckrapp added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label Jul 6, 2022
@MatomoForumNotifications
Copy link

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/why-are-numbers-of-tracked-visits-changed-retrospective/46529/2

@bx80
Copy link
Contributor

bx80 commented Jul 11, 2022

Hi @ckrapp, it's hard to know why the figures could have changed without more information. In normal usage, once a month has passed it's archived data should not be processed again. Did you install any new plugins? Was there any re-archiving / archive invalidation done? Did you create any new segments?

It could be that the archiving process for those months was interrupted or failed to complete for some reason and then a change triggered re-archiving which corrected the figures. (or visa-versa)

If you have logs from the archiving cronjob then it might be worth checking them to see if there are any errors being logged. You could also manually invalidate and re-archive the those months to confirm that the updated figures are correct and that there are no archiving issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced.
Projects
None yet
Milestone
For Prioritization
Development

No branches or pull requests
4 participants
@bx80 @MatomoForumNotifications @ckrapp @innocraft-automation