-
Notifications
You must be signed in to change notification settings - Fork 209
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
Behavioral filtering docs #575
Conversation
@@ -247,6 +248,20 @@ Filters can be combined using `and`, `or` and `not` operators. | |||
|
|||
Note that top level filters is wrapped in an implicit `and`. | |||
|
|||
#### Behavioral filters | |||
|
|||
Behavioral filters can be used to filter whether a user has ever done or not done something. This can be used to filter out users who have not completed a goal or |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick, non-blocking: the word "ever" here might give the impression that a user is identifiable (and their actions on site traceable) for longer than they actually are.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
best just to talk about a segment of audience rather than a user. that's what we typically do across the site
"date_range": ["2025-01-10T00:00:00+00:00", "2025-01-16T23:59:59+00:00"], | ||
"filters": [ | ||
["is", "event:page", ["/pricing"]], | ||
["has_done", ["is", "event:goal", ["Open Support Chat"]]], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suggestion, non-blocking: This line might be a good opportunity to show off event:name filter as well.
Closing for now - behavioral filters are (for now) internal only. Will resurrect when this becomes a public API feature. |
Main PR: plausible/analytics#4980