From 0310d033da3f40be706efe4e701a7907e76e8da2 Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Fri, 27 Dec 2024 16:18:36 -0500 Subject: [PATCH 1/3] Update index.md --- src/connections/sources/schema/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/connections/sources/schema/index.md b/src/connections/sources/schema/index.md index db31e9ba17..9b75ea06e5 100644 --- a/src/connections/sources/schema/index.md +++ b/src/connections/sources/schema/index.md @@ -39,6 +39,8 @@ If you no longer want to track a specific event, you can either remove it from y > info "" > For sources with a connected Tracking Plan, use Protocols to block unplanned events. +>info "" +> After blocking events, you will still see these events being ingested into the debugger with a block symbol. This gives insight to the events that are being blocked by Segment. 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. From 38528745e085475219d8f409d761240cc0909cf1 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 23 Jan 2025 15:09:52 -0600 Subject: [PATCH 2/3] moving this out of an info box --- src/connections/sources/schema/index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/connections/sources/schema/index.md b/src/connections/sources/schema/index.md index 9b75ea06e5..903efb3363 100644 --- a/src/connections/sources/schema/index.md +++ b/src/connections/sources/schema/index.md @@ -31,7 +31,7 @@ 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") @@ -39,15 +39,13 @@ If you no longer want to track a specific event, you can either remove it from y > info "" > For sources with a connected Tracking Plan, use Protocols to block unplanned events. ->info "" -> After blocking events, you will still see these events being ingested into the debugger with a block symbol. This gives insight to the events that are being blocked by Segment. - 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 From 488045a219fc3058ad380e3b0dc2817a1dcbc9c8 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 23 Jan 2025 15:10:07 -0600 Subject: [PATCH 3/3] forgot a period --- src/connections/sources/schema/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/sources/schema/index.md b/src/connections/sources/schema/index.md index 903efb3363..33328d846e 100644 --- a/src/connections/sources/schema/index.md +++ b/src/connections/sources/schema/index.md @@ -45,7 +45,7 @@ When an event is blocked, the name of the event or property is added to your Sch 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 +Blocked events appear in the debugger with a block symbol, adding visibility into events actively blocked by Segment. ## Identify and Group Trait Filters