Filter ingested data

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 pipelines add-on, or a self-hosted PostHog instance running a recent version of the Docker image.

Installation

1. In PostHog, click the "Data pipeline" tab in the left sidebar.
2. Search for 'Filter Out' and select the transformation, press Install.
3. 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:

FAQ

Q: How can I filter out events from unwanted hostnames or IP addresses?

To filter out all traffic from hosts that are not (for example) posthog.com, you could use the following config:

[
  {
    "property": "$host",
    "type": "string",
    "operator": "is",
    "value": "posthog.com"
  }
]

Or, to filter out all traffic from a particular IP address, you could use a config like this example:

[
    {
        "property": "$ip",
        "type": "string",
        "operator": "is_not",
        "value": "192.168.01.123"
    }
]

Make sure to enable the Keep event if any of the filtered properties are undefined? option, otherwise, any events where the $host property is undefined will be filtered out.

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.