Drop events

Last updated:

|Edit this page

PostHog's drop events transformation allows you to selectively discard events from being ingested based on specific criteria.

Overview

The drop events transformation permanently removes events from your data pipeline, preventing them from being stored or processed by PostHog.

Configuration

The drop events transformation uses filters to target specific events for removal.

Filtering options

  1. Event matching: Target specific event types by name (e.g., $pageview, user_signed_up)
  2. Property filters: Further refine your filters with property conditions:
    • Match on any event property
    • Supports operators like equals, contains, greater than, etc.
    • Apply property filters globally across all events or specifically to individual event types

How to use the filters

The drop events transformation uses two types of filters that work together:

  1. Match events filters: These filters operate with OR logic. If an event matches ANY of these filters, it will be considered for dropping. For example, if you select both $pageview and $pageleave events, the transformation will match events of either type.

Drop events based on event filters

  1. Property filters: These filters use AND logic and are applied after the event matching. ALL property conditions must be met for an event to be dropped. For example, if you set:

    • browser is set
    • Country Name is set

    Only events that have BOTH properties matching these conditions will be dropped.

Drop events based on property filters

  1. Property filters on event match filter: You can add property filters directly to event match filters. For example:
    • If you select "All events" and add a property filter "browser is set", it will drop ALL events that have the browser property set
    • If you also add specific event matches like $pageview and $pageleave, it will drop:
      • All $pageview events
      • All $pageleave events
      • Any other events that have the browser property set

Drop events based on combined filters

Example of combined filters

Let's say you configure the following:

Match events:

  • $pageview
  • user_signed_up

Property filters:

  • browser is set
  • Country Name is set

This configuration will drop:

  • Any $pageview events that have both browser and country name properties set
  • Any $pageleave events that have both browser and country name properties set

Events that don't meet ALL these criteria (like a $pageview missing the browser property, or a $pageleave event missing the country name) will not be dropped.

Testing

Before enabling your drop events transformation in production, use the built-in testing interface to verify it works as expected:

  1. Go to the Testing section of your transformation
  2. Select an event to test with
  3. Run the test to see if the event would be dropped
  4. Iterate on your filters until you're satisfied with the results

Important considerations

  • Permanence: Dropped events are permanently deleted and cannot be recovered
  • Monitoring: Check the metrics and logs tabs regularly to ensure the transformation is working as expected

Learn more

Questions? Ask Max AI.

It's easier than reading through 627 docs articles.

Community questions

Was this page useful?

Next article

Troubleshooting and FAQs

My transformation or destination isn't working, what do I do? Wait 60 seconds, then check that the transformation or destination is enabled with the correct configuration options in the data pipeline tab . You can find the correct configuration options in the transformation or destination's documentation by searching for it in the destinations, transformations, or filtering sections of the docs. Click "Logs & metrics" and go to the Metrics tab to check that the transformation or destination…

Read next article