PostHog / PostHog/posthog

Cross-experiment user / exposure view

Open
#67,208 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team/experiments
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

Is your feature request related to a problem?

For power users with many (sometimes overlapping) experiments, there's no way to see, for a
person, all experiments they were exposed to and with which variants — nor to reason about interaction effects when a user sits in several experiments at once.

Describe the solution you'd like

  • Person → experiments view/API. Given a person, list experiments + variants + exposure times.
  • Overlap / interaction analysis (stretch) - Surface users in ≥2 concurrent experiments and flag potential interaction effects.

Additional context

Customer cares about where a user has been in all experiments or not, and wants to see behaviour based on this.

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

Start by mapping the existing experiment and exposure-data entry points relevant to a person, including where variants and exposure times are available. Define done as a person-level view or API listing all experiments, variants, and exposure times; overlap analysis is explicitly a stretch goal.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.