Event Blocking

Event Blocking is now generally available for Enterprise and Growth plans. It lets you stop unwanted events before they enter your data pipelines, helping you maintain clean data capture and reduce billable event volume. Blocking applies globally across all sources in your workspace.

Event Blocking is available on the Growth plan for up to 2 blocked events and on the Enterprise plan for unlimited blocked events.

Why Event Blocking?

Unwanted events can enter your pipelines when mobile SDKs collect lifecycle events you do not need, application bugs create an overflow of events, or deprecated and incorrectly instrumented events remain in production. Event Blocking gives you a direct way to drop these events while you address the underlying instrumentation. Because blocked events are dropped before entering your data pipelines, they do not count toward billable event volume.

Key features

• Block events before ingestion: Drop selected events before they enter your data pipelines so they do not flow to downstream systems.
• Apply blocking globally: Block an event name across all sources in your workspace instead of configuring the rule for each source.
• Match by event name: Choose the event name to block, with blocking limited to track events.
• Monitor blocked volume: View blocked-event metrics for individual sources, including the event name, block count, and when RudderStack last blocked the event.
• Control billable volume: Blocked events do not count toward your billable event volume.

Event blocking results in permanent data loss. Blocked events cannot be replayed or recovered, so confirm that an event has no current or future value before blocking it.

Get started

1. In the RudderStack dashboard, go to Govern > Event Blocking.
2. Enable event blocking for your workspace.
3. Add the track event names that you want to block.
4. Review source-level blocked-event metrics from the Events tab of a source.

See the Event Blocking documentation for complete configuration instructions and considerations.

Resources

• Event Blocking overview: Learn how blocked events are handled before they enter your data pipelines.
• Configure Event Blocking: Add or remove blocked events from the Event Blocking page or Data Catalog.
• View source-level blocked-event metrics: Monitor blocked volume and event details for a source.
• Event Blocking limitations: Review event type, matching, scope, plan, and data loss constraints.