You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/schema-defaults-eol.md
+6-24Lines changed: 6 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,43 +5,25 @@ hidden: true
5
5
6
6
## Schema Defaults Removal FAQs
7
7
8
-
Schema Defaults allows you to block new events and traits by default. This feature was launched to Private Beta in 2017 as an exploration feature before the introduction of Protocols. It will be removed on August 11, 2021.
9
-
10
-
#### How do I know if I’m using Schema Defaults?
11
-
Navigate to **Connections** and choose your source. In the **Settings** tab under **Schema Configuration**, if you see the **Schema Defaults** section and have any events or traits that are marked **Block** or **Omit**, you have Schema Defaults enabled.
Schema Defaults allows you to block new events and traits by default. This feature was launched to Private Beta in 2017 as an exploration feature before the introduction of Protocols.
14
9
15
10
#### What happens after Schema Defaults is removed?
16
11
Any events and traits that were blocked by Schema Defaults will continue to be blocked. Any new events and traits will automatically be allowed.
17
12
18
-
Before they are removed, you can change your Source Schema settings to allow or block individual events, properties, and traits by following these steps:
19
-
20
-
1. Go to the **Schema** tab of your source.
21
-
2. Use the toggle to allow or block the different events, properties, and traits.
If you still want to block new events and traits by default, you can connect a [Protocols Tracking Plan](/docs/protocols/) to your source.
24
14
25
15
#### What happens if a source with Schema Defaults enabled has a Tracking Plan connected to it?
26
-
Tracking Plans_replace_ Schema Defaults, so these sources will continue to behave the same.
16
+
[Tracking Plans](/docs/protocols/tracking-plan/) replace Schema Defaults, so these sources will continue to behave the same.
27
17
28
-
#### How should I prepare for the removal of Schema Defaults?
29
-
If you still want to block new events and traits by default, you can connect a [Protocols Tracking Plan](/docs/protocols/) to your source.
30
18
31
19
## Event Requirements Removal FAQs
32
20
33
-
Event Requirements allow you to define rules for an event property and block violating events. This feature was launched to Private Beta in 2017 as an exploratory feature before the introduction of Protocols. It will be removed on August 11, 2021.
34
-
35
-
#### How do I know if I’m using Event Requirements?
36
-
Navigate to **Connections** and choose your source. Go to the **Schema** tab and click on an event. If you’re able to click on an event and view the properties and rules for it, you’re using Event Requirements.
Event Requirements allow you to define rules for an event property and block violating events. This feature was launched to Private Beta in 2017 as an exploratory feature before the introduction of Protocols.
39
22
40
23
#### What happens after Event Requirements is removed?
41
24
Events that violate the rules set up in Event Requirements will no longer be blocked. The Event Requirements UI will be removed from the Segment web app, and you won’t be able to interact with the feature settings.
42
25
26
+
If you still want to block the events that you set up in Event Requirements, you can connect a [Protocols Tracking Plan](/docs/protocols/tracking-plan/) to your source.
27
+
43
28
#### What happens if a source with Event Requirements enabled has a Tracking Plan connected to it?
44
29
[Tracking Plans](/docs/protocols/tracking-plan/) replace any Event Requirements, so these sources will continue to behave the same.
45
-
46
-
#### How should I prepare for the removal of Event Requirements?
47
-
If you still want to block the events that you set up in Event Requirements, you can connect a [Protocols Tracking Plan](/docs/protocols/tracking-plan/) to your source.
0 commit comments