This transformation enables you to create filters which prevent PostHog from ingesting data from your product unless it passes those filters. Any events which do not match the filter requirements are skipped over and are not ingested.
Requirements
Using this requires either PostHog Cloud with the data pipeline add-on, or a self-hosted PostHog instance running version 1.30.0 or later.
Self-hosting and not running 1.30.0? Find out how to update your self-hosted PostHog deployment.
Installation
- In PostHog, click the "Data pipeline" tab in the left sidebar.
- Search for 'Filter Out' and select the transformation, press Install.
- Follow the on-screen steps to configure the transformation.
This transformation will only work on events ingested after the transformation was enabled.
Configuration
The transformation can be configured via a JSON file which specifies the properties you would like to filter.
In the example config below, the transformation will only keep events where all of the following conditions are met:
- Email does not contain yourcompany.com
- Host is not localhost:8000
- Browser version greater than 100
[{"property": "email","type": "string","operator": "not_contains","value": "yourcompany.com"},{"property": "$host","type": "string","operator": "is_not","value": "localhost:8000"},{"property": "$browser_version","type": "number","operator": "gt","value": 100}]
The followed types and operators are allowed:
Type | Operators |
---|---|
number | gt, gte, lt, lte, eq, neq |
string | is, is_not, contains, not_contains, regex, not_regex |
boolean | is, is_not |
FAQ
Who maintains this?
This is maintained by the community. If you have issues with it not functioning as intended, please let us know!
What if I have feedback on this destination?
We love feature requests and feedback. Please tell us what you think..
What if my question isn't answered above?
We love answering questions. Ask us anything via our community forum.