Skip to content

Incorrect visitors/visits/views_per_visit when filtering by event:page #6260

@dangolomysov

Description

@dangolomysov

Past Issues Searched

  • I have searched open and closed issues to make sure that the bug has not yet been reported

Issue is a Bug Report

  • This is a bug report and not a feature request, nor asking for self-hosted support

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

Image

Environment

- OS:
- Browser:
- Browser Version:
Using r2024.02.20-361 version

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions