PostHog / PostHog/posthog

Support exclusion criteria in experiment exposure

Open
#29,192 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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?

A customer is running an experiment that moves their sign-up stage later in the funnel to measure its impact on new customer acquisition. However, they need to exclude users who log in at that stage, as they are already existing customers. Currently, there is no built-in way to filter out those users, which can affect the accuracy of experiment results.

Describe the solution you'd like

Introduce exclusion criteria in experiment exposure. This would allow teams to filter out users based on specific behaviors (e.g., logging in), ensuring that only relevant users are included in the experiment.

Additional context

Zendesk ticket https://posthoghelp.zendesk.com/agent/tickets/25834 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/27798)

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

The issue names no files, tests, or entry points, so begin by asking maintainers where experiment exposure is implemented and whether existing filtering tests cover it. Before coding, clarify the supported exclusion criteria and acceptance checks; completion should be defined with maintainers.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.