Skip to content

Commit cdfb331

Browse files
author
markzegarelli
authored
Updated content to reflect impact of Tracking Plans (#3058)
1 parent 842cfcf commit cdfb331

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

src/protocols/schema.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,14 @@ Segment Business plan customers can use Schema Controls to manage which events a
99

1010
## Event filters
1111

12-
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, you can block track calls right 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.
12+
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.
1313

1414

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

17+
> info ""
18+
> For sources with a connected Tracking Plan, use Protocols to block unplanned events.
19+
1720

1821
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.
1922

0 commit comments

Comments
 (0)