-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[Bug] Incorrect figures in customer reports #22756
Comments
Hey @klbrnd, would you mind attaching some screenshots of the reports where you found not matching numbers? Thanks |
Hello!
Here are the screenshots. The first (campaign-sources_1.jpg) shows the figures under campaigns and the second shows the figures in the custom reports.
As you can see, the numbers are different for the same time period.
I hope this helps. Let me know if you need anything else.
BR
|
Hi @klbrnd, I don't think the screenshots were uploaded properly. Could you please try again? Thanks. |
Hi @klbrnd, Could you please create a custom report by filtering the campaign source to the one which is mismatched and check again? If this is the case, you will need to change the row limit - https://matomo.org/faq/custom-reports/faq_25655/ |
@klbrnd Was the custom report created recently ? Asking this Q as you are viewing the data from 2024-01-01, if the custom report is created recently, you might need to run this console command to archive reports data for older dates.
|
What happened?
unfortunately, the customer reports do not show the same figures as the normal reports. for example, for the sources. there seems to be a problem with the transfer or sorting
What should happen?
correct figures in customer reports
How can this be reproduced?
check campaign source and source in customer report. they are not identical.
Matomo version
5.1.2
PHP version
No response
Server operating system
No response
What browsers are you seeing the problem on?
Chrome
Computer operating system
windows
Relevant log output
No response
Validations
The text was updated successfully, but these errors were encountered: