Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
#6,260 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
42/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
elixir
Área
analytics

Línea de trabajo

Start by reproducing the discrepancy with an event:page filter and matching date range, comparing top stats, visitors.csv, and visit-property breakdowns such as source or country. Trace how each result defines its filtered population and verify that visitors, visits, pageviews, and views_per_visit use compatible populations; done means the metrics are internally consistent.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Elixir
Estrellas
29.7k
Forks
1.9k
Merge medio
3 d 22 h
PR fusionados (30 d)
50

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de plausible/analytics

Todos los issues de plausible/analytics

Issues similares

Más issues de Elixir

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.