PostHog / PostHog/posthog

Feature Request: Funnels - entity-scoped step matching by shared event property

Open
#66,096 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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?

When tracking a user's journey through our B2B SaaS, I want to know that events being sent all relate to the same object. Our software is eSigning. Our funnel goes document upload -> sent for signing -> signed. I want to be sure that when I track this funnel, the document that was created is the same as the document that was sent for signing is the same as the document that was signed. I can add the document_uuid as a property to all 3 events but then in the funnel I can't do anything with that.

Describe the solution you'd like

A setting in funnels to say that the user and some other property(s) must match for an event to be included.

Describe alternatives you've considered

PostHog AI suggested breakdown by document_uuid, which is too granular to properly read, and a SQL insight which is much harder to setup and can't be inspected interactively like the native funnels.

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 named. Begin by finding the funnel configuration and event-matching implementation; completion should support requiring the user and one or more shared properties to match across steps, with the result usable in interactive funnels.

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.