Skip to content

Commit

Permalink
Merge pull request #7360 from segmentio/jfoskin-patch-2
Browse files Browse the repository at this point in the history
Add info on blocked events in the debugger
  • Loading branch information
pwseg authored Jan 23, 2025
2 parents 6793620 + 488045a commit dc37d89
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions src/connections/sources/schema/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,21 +31,21 @@ The Source Schema UI changes slightly depending on whether you have a [Protocols
## Event filters

If you no longer want to track a specific event, you can either remove it from your code or, if you're on the Business plan and don't have a Tracking Plan connected, you can block track calls from the Segment UI. To do so, click on the Schema tab in a Source and toggle the event to enable or block an event.
If you no longer want to track a specific event, you can either remove it from your code or, if you're on the Business plan and don't have a Tracking Plan connected, you can block track calls from the Segment UI. To do so, click on the Schema tab in a Source and toggle the event to enable or block an event.


![Event filters](images/event-filters.png "Event filters in Segment")

> info ""
> For sources with a connected Tracking Plan, use Protocols to block unplanned events.

Once you block an event, Segment stops forwarding it to all of your Cloud and Device-mode Destinations, including your warehouses. You can remove the events from your code at your leisure. In addition to blocking track calls, Business plan customers can block all Page and Screen calls, as well as Identify traits and Group properties.

When an event is blocked, the name of the event or property is added to your Schema page with a counter to show how many events have been blocked. By default, data from blocked events and properties is not recoverable. You can always re-enable the event to continue sending it to downstream Destinations.

In most cases, blocking an event immediately stops that event from sending to Destinations. In rare cases, it can take **up to six hours** to fully block an event from delivering to all Destinations.

Blocked events appear in the debugger with a block symbol, adding visibility into events actively blocked by Segment.

## Identify and Group Trait Filters

Expand Down

0 comments on commit dc37d89

Please sign in to comment.