-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explain how identical funnel steps work in the UI #5088
Comments
We'd have to see with users, but that does sound like a sensible and simple solution. |
Love @mariusandra's idea, though I would still add a tooltip (probably a |
I'll pick this up if no one else can |
Flyby comment: there is also a difference in returned data depending on whether you're running the query on psql or Clickhouse — am I correct @EDsCODE ? |
Yeah, iirc our postgres implementation doesnt support identical event differentiation like clickhouse does |
Is your feature request related to a problem?
Currently users get confused by the way identical funnel steps work. When two or more steps are identical one after another, they sometimes expect there to be no dropoff from identical step 1 to identical step 2.
But the way it really works (shown below) is much more practical:
What PostHog does instead, is that out of the set of people who performed the step once (making up step 1), for step 2 it counts people who performed that step for a second time in the funnel window. This way it's possible to construct funnels requiring a user to perform a specific action n times before carrying on with the rest of the funnel.
Describe the solution you'd like
If a step is identical to the previous one, it should have a tooltip (over an ℹ️ icon maybe) explaining why there's a dropoff.
Additional context
See #5046 or https://posthog.slack.com/archives/C0113360FFV/p1626110518064100.
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: