Feature Request: Make window visibility events queryable within PostHog
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by tracing how window visibility events are stored in session replay data, then inspect the query paths for insights and SQL. The work is done when these events can be selected and aggregated through both insights and SQL, rather than only viewed in recordings.
Written by the indexing model from the issue text.
Description
Feature request
Is your feature request related to a problem?
We store window visibility events in session replay data, but that's not queryable anywhere outside recordings.
The window being hidden can be a leading indicator that there is a high risk for abandonment in the session/journey they are on. So understanding how features impact users feeling the need to hide the window because they are waiting for extended period of times is a valuable metric.
Describe the solution you'd like
Make window visibility events queryable in insights and SQL.
Describe alternatives you've considered
- Use replays to see them, but that lacks aggregation/analysis.
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/34887 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/36541)
Debug info
null
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PostHog/posthog
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
MotherDuck incremental sync never checks for duplicate primary keys, so the guard is a dead branch Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100