More find/delete

Steve van Loben Sels · Steve van Loben Sels · commit 0b4237a21f9c · 2021-05-05T15:28:58.000-07:00
diff --git a/src/guides/filtering-data.md b/src/guides/filtering-data.md
@@ -68,25 +68,6 @@ The events filtered out of individual destinations using this method still arriv
 
 **Integration filters are all-or-nothing for each event.** If you require more detailed control over which events are sent to specific destinations, you can use Destination Filters to inspect the event payload, and conditionally drop the data or forward it to the destination.
 
-## Schema Defaults
-
-Schema defaults allow you to prevent unexpected or malformed data from a Source from getting into your downstream destinations. When you set your Schema Defaults to **Block**, Segment automatically prevents new Events from being sent to destinations. You can activate this for new events (including `track`, `page`, and `screen` events) or for new `identify` traits and `group` properties.
-
-Data blocked using schema defaults is permanently discarded, and cannot be recovered or replayed through Segment. You can forward blocked data to a new Source, but these events count toward your account MTU limits, and may not be worth saving.
-
-Schema Defaults are only available to Business Tier customers.
-
-You can find the Schema Defaults in the **Settings** tab for each Source, in **Schema Configuration** section.
-
-![](images/schema-defaults.png)
-
-**Schema Defaults Blocking Limitations**
-You cannot use Schema defaults if the source is connected to a Tracking Plan. If you're using Protocols and Tracking Plans, use [Protocols Tracking Plan Blocking](#protocols-tracking-plan-blocking-and-property-omission) to perform the same blocking. Learn more in the [Protocols Schema Configuration documentation](/docs/protocols/enforce/schema-configuration/).
-
-**Track** events blocked by Schema filters are not delivered to either device-mode or cloud-mode Destinations. That means if you send a blocked event from a client-side library like Analytics.js, it is not delivered to any device-mode Destinations.
-
-**Identify** and **Group** call traits blocked by Schema filters are **only** blocked from delivering to cloud-mode Destinations. Since device-mode destinations are connected directly to the user's device and don't pass through the Segment filters first, they still receive all traits regardless of whether they are blocked in the Segment Schema.
-
 ## Schema Event Filters
 
 You can use Schema Event Filters to discard and permanently remove Page, Screen and Track events from event-based sources, preventing them from reaching any destinations or warehouses. Use this if you know that you'll never want to access this data again. This functionality is similar to filtering with the Integrations object, however it can be changed from within the Segment app without touching any code.
diff --git a/src/protocols/schema.md b/src/protocols/schema.md
@@ -54,78 +54,3 @@ Segment Business tier customers can block track calls from delivering to specifi
 
 
 ![](images/asset_d3SRmkWy.gif)
-
-## Schema Defaults
-
-Whether you're just about to implement a new spec or you have been tracking the same events for years, Schema Defaults make it easy to protect your data and fix data quality issues.
-
-Schema Defaults offers a quick and easy way to prevent unexpected or erroneous events from reaching your destinations. When you set Schema Defaults to **Block**, Segment automatically prevents new calls from being sent downstream. You can activate this for new events—including `track`, `page`, and `screen` calls, or for new `identify` traits and `group` properties.
-
-Locking your schema only takes a few seconds and prevents new rogue events from polluting your Destinations. To configure Schema Defaults, go to your source Settings page, and select **Schema Configuration** from the left-hand navigation.
-
-### When should I lock my schema?
-
-Here are a few signs you may be ready to lock your schema:
-
-- You are concerned about developers implementing rogue events
-- You want to actively approve which events are tracked and routed to your downstream Destinations
-- You have created a tracking plan and want to use Segment to enforce it
-
-![](images/asset_A8jUVuph.gif)
-
-
-### Overview of Schema Default settings
-
-| Setting              | Allow                                                                | Block                             |
-| -------------------- | -------------------------------------------------------------------- | --------------------------------- |
-| New Events           | All new events are allowed in Segment and sent to all Destinations.| No new events are allowed in Segment or sent to your cloud and device-mode Destinations. Any event that is already being tracked and part of your Schema is not impacted. |
-| New Group Properties | All new group properties are allowed in Segment and sent to all Destinations. | No new group properties are allowed in Segment or sent to your cloud-mode Destinations. Device-mode destinations **do** receive blocked traits. |
-| New Identify Traits  | All new identify traits are allowed in Segment and sent to all Destinations.  | No new identify traits are allowed in Segment or sent to your cloud-mode Destinations. Device-mode destinations **do** receive blocked traits.|
-
-
-### Schema Default Blocking support across connection modes
-
-Track events blocked by Schema filters are prevented from delivering to both device-mode and cloud-mode Destinations. That means if you send a blocked event from a client side library like Analytics.js, it is not delivered to any device-mode Destinations.
-
-Identify and group call traits blocked by Schema filters **only** blocked from delivering to cloud-mode Destinations. Device-mode destinations receive all traits regardless of whether they are blocked in Schema.
-
-
-
-### What is considered a "new" event?
-
-New events refer to events that have not previously been sent to a given Source. Let's say you've only sent the following events from your Javascript source:
-
-- `Products Searched`
-
-- `Product List Viewed`
-
-- `Product List Filtered`
-
-Your Schema Default setting does not block these three events because they are not considered new. You can manually block them, but your Schema Default setting does not change the status of these events. 
-
-Here's what happens the first time a new event, `Promotion Viewed`, is sent to this Source:
-
-- **Schema Default Set to Allow:** `Promotion Viewed` is allowed, which means the event is sent to all enabled Destinations.
-
-- **Schema Default Set to Block:** `Promotion Viewed` is blocked, which means the event is not sent to any Destinations.
-
-
-## Blocked Track Event forwarding
-
-If you're concerned about permanently discarding blocked track events, you can forward blocked track events to a new Segment Source. To enable, go to Source Settings > Schema Configuration and select which Source you want to forward track events to from the drop down. We recommend [creating a new Source](https://segment.com/docs/guides/general/what-is-a-source/) for forwarded events to avoid contaminating production data.
-
-![](images/advanced-settings.png)
-
-**NOTE: Only blocked `.track()` events are forwarded to the source. `.identify()` and `.group()` events are not forwarded.**
-
-**BILLING NOTE: Events forwarded to a Segment Source count towards your MTU counts. Blocking and discarding events do not contribute to your MTU counts.**
-
-## Blocked event billing
-
-Your bill is based on the number of Monthly Tracked Users (MTU). MTUs are the number of identified and anonymous users that you track with Segment. We only count users once per month, even if they perform multiple actions across your site or app. In most cases, blocked events have no impact on your MTU count as they are not stored or sent downstream. If you enable Blocked Event Forwarding, the forwarded events contribute to your MTU count.
-
-## Blocked event notifications
-
-While protecting the integrity of your data is helpful with event blocking and Schema Defaults, we offer proactive notifications to flag new blocked events so you can make any needed changes in your code or approve a new event.
-
-Your workspace notifications alert you when a new event is blocked due to your Schema Defaults. You can enable notifications in the [Notification Settings](https://app.segment.com/goto-my-workspace/settings/notifications) of your workspace.
diff --git a/src/protocols/validate/connect-sources.md b/src/protocols/validate/connect-sources.md
@@ -13,7 +13,7 @@ With your Tracking Plan is complete, it's time to apply the Tracking Plan to one
 
 From this menu, you will be redirected to a workflow to select a Source from your workspace. Note that a Source can only have one tracking plan applied to it. You *can't* select a Source that already has a Tracking Plan connected to it, but you *can* apply a Tracking Plan to multiple sources.
 
-After selecting a Source, you will be shown the consequences of connecting your Tracking Plan. In many cases, there will be no consequences. However, if you've enabled Schema Defaults, events previously allowed will now be blocked if they are not included in the Tracking Plan. If you've blocked specific events, those events will now be allowed until you enable Blocking in the Tracking Plan settings.
+After selecting a Source, you will be shown the consequences of connecting your Tracking Plan.
 
 **IMPORTANT: Make sure to read through the consequences of connecting a source!**
 
