Past Issues Searched
Issue is a Bug Report
Using official Plausible Cloud hosting or self-hosting?
Self-hosting
Describe the bug
When filtering the dashboardby a specific page (event:page), Plausible appears to return inconsistent results across:
- top stats /
visitors.csv
- visit-property breakdowns such as sources, countries, browsers, OS, entry pages, etc.
For example:
Using page-filter: number of unique visitors in top-stats >> number of total visits in top-stats.
And total number of visitors in breakdowns (e.g, by source), differs with the unique visitors in top stats (other breakdowns -(source, country, browser, os, entry_page, etc.) displays the same problem).
This makes it look like page-filtered top stats/export and page-filtered visit-property breakdowns are not operating on the same underlying population.
Expected behavior
Under the same event:page filter and date range:
- top-level metrics should be internally consistent;
views_per_visit should be consistent with pageviews / visits;
- visit-property breakdowns (
source, country, browser, os, entry_page, etc.) should be derived from a compatible page-filtered population and should not represent a dramatically smaller visitor universe than the top-level visitor count.
I understand that unique visitors are non-additive across buckets, so I am not expecting exact equality between “total visitors” and “sum of visitors per bucket”.
The bug is that the populations themselves appear inconsistent under event:page.
Screenshots
Environment
- OS:
- Browser:
- Browser Version:
Using r2024.02.20-361 version
Past Issues Searched
Issue is a Bug Report
Using official Plausible Cloud hosting or self-hosting?
Self-hosting
Describe the bug
When filtering the dashboardby a specific page (
event:page), Plausible appears to return inconsistent results across:visitors.csvFor example:
Using page-filter: number of unique visitors in top-stats >> number of total visits in top-stats.
And total number of visitors in breakdowns (e.g, by source), differs with the unique visitors in top stats (other breakdowns -(
source,country,browser,os,entry_page, etc.) displays the same problem).This makes it look like page-filtered top stats/export and page-filtered visit-property breakdowns are not operating on the same underlying population.
Expected behavior
Under the same
event:pagefilter and date range:views_per_visitshould be consistent withpageviews / visits;source,country,browser,os,entry_page, etc.) should be derived from a compatible page-filtered population and should not represent a dramatically smaller visitor universe than the top-level visitor count.I understand that unique visitors are non-additive across buckets, so I am not expecting exact equality between “total visitors” and “sum of visitors per bucket”.
The bug is that the populations themselves appear inconsistent under
event:page.Screenshots
Environment