-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Support "Path cleaning rules" in trends & heatmaps #7288
Labels
Comments
macobo
added
feature/paths
Feature Tag: Paths
feature/toolbar
Feature Tag: Toolbar
labels
Nov 23, 2021
thmsobrmlr
added
feature/trends
Feature Tag: Trends
and removed
feature/paths
Feature Tag: Paths
labels
Jan 20, 2023
Yo, seems like this doesn't work with query params -- is that correct and by design? Trying to configure a User Paths insight and utm params are preventing the paths from grouping. |
Shouldn't be the case, as long as you have a wildcard in the right place 🤔 - mind opening a separate issue about the exact problem you're facing? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem?
You have recently added the concept of "Path cleaning rules" to support multi-tenanted systems in the User Paths insight. It would be great if this concept could be expanded to other use-cases in the PostHog application.
Describe the solution you'd like
Trends
We would like an easy way to find the popular pages on our site, if we breakdown by
Current URL
, it does not work as it treats/merchant/123/dashboard
separate from/merchant/321/dashboard
. Using the Path cleaning rules, we would see a total number for/merchant/*/dashboard
.Heatmaps
We would like to see the heatmaps of pages on our site. Currently it does not work as it as it treats
/merchant/123/dashboard
separate from/merchant/321/dashboard
meaning we get a heatmap for each page. Using the Path cleaning rules, we would see one heatmap for/merchant/*/dashboard
.Describe alternatives you've considered
Manually run this analysis somehow.
Additional context
Thank you for your feature request – we love each and every one!
The text was updated successfully, but these errors were encountered: