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/protocols/faq.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -76,9 +76,9 @@ If you [discarded events](/docs/protocols/enforce/schema-configuration) as a par
76
76
77
77
Unfortunately, Sources cannot be connected to more than one Tracking Plan. If you were able to connect more than one Tracking Plan to a Source, it could create conflict if events overlapped.
78
78
79
-
## How is the Track Plan implemented?
79
+
## How does Tracking Plans work behind the scenes?
80
80
81
-
The Tracking Plan is included in the source settings. Essentials, Segment has logic in the code that checks to see if an event is in the Tracking Plan.
81
+
Segment's code has built-in logic that verifies if an event exists in the Tracking Plan and if not, it will follow the configuration the Schema Configuration settings for each source connected to the Tracking Plan.
0 commit comments