PostHog / PostHog/posthog

Feature Request: group viewports to avoid too many values

Open
#41,571 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team/web-analytics
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Feature request

Is your feature request related to a problem?

Viewport sizes are treated too granularly (e.g., 1920×1080 vs. 1919×1080), causing users to be split across many tiny buckets.

Describe the solution you'd like

  • Implement viewport grouping / bucketing so slightly different resolutions are merged (e.g., rounding widths/heights to the nearest 8-10–16px). This would make totals align with overall visitor counts and improve readability.

Describe alternatives you've considered

Define fixed viewports and doing a lookup on them.

Additional context

https://posthoghelp.zendesk.com/agent/tickets/42646 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/44410)

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the linked Zendesk and PostHog support tickets, then clarify the bucketing rule and how it should compare with fixed viewports. Done means slightly different resolutions are merged while totals align with overall visitor counts and remain readable.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.