Skip to content

Commit dc37d89

Browse files
authored
Merge pull request #7360 from segmentio/jfoskin-patch-2
Add info on blocked events in the debugger
2 parents 6793620 + 488045a commit dc37d89

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/connections/sources/schema/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,21 +31,21 @@ The Source Schema UI changes slightly depending on whether you have a [Protocols
3131
3232
## Event filters
3333

34-
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.
34+
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.
3535

3636

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

3939
> info ""
4040
> For sources with a connected Tracking Plan, use Protocols to block unplanned events.
4141
42-
4342
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.
4443

4544
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.
4645

4746
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.
4847

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

5050
## Identify and Group Trait Filters
5151

0 commit comments

Comments
 (0)