PostHog / PostHog/posthog

Experiment tags (manual + auto-tagging) ⟵ foundational

Open
#67,206 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?

Orgs grow fast and fall behind on experiment hygiene; large numbers of experiments go unorganized. A simple tagging system lets teams group/filter; auto-tagging on creation keeps it low-effort so process doesn't depend on discipline. We have tagging on FF, so should provide this as parity.

Describe the solution you'd like

When a user creates an experiment we should add the ability to add tags. We could do auto-tags, but question is whether the AI using the MCP can add these, or PHC. If we added an autotagger we could ensure tag consistency.

Describe alternatives you've considered

Additional context

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 identified in the issue. First clarify the experiment-tagging model and whether manual tags, automatic tags, or both are in scope, including whether tagging is handled by MCP or PHC; done should include an agreed creation flow and consistent tag behavior.

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.