-
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
Group events and page views into categories #2334
Comments
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the |
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant. |
This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the |
This issue was closed due to lack of activity. Feel free to reopen if it's still relevant. |
Is your feature request related to a problem?
User tasks can be categorised into certain groups or page views and events. Posthog doesn't allow us to group these into one category at the moment, e.g. administrative tasks like adding a new user to the system take place on a certain page with certain events. Being able to quickly find all events and pages that are in this group would help organise the list of pages and events as well as run analytics on these groups. Which users performed admin tasks - could lead to a cohort (admins). Which sessions were admin focused - shows users who seem to only administer the system, but don't use it otherwise.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Posthog tracks (almost) every event that a user performs within the product. This is a flood of information. Being able to group, would allow me to step back a level. Especially when verifying my assumptions.
This would also help find specific actions after defining a large number, first filter on category, then find the action.
Thank you for your feature request – we love each and every one!
Right back at you - Posthog team.
The text was updated successfully, but these errors were encountered: