Merge pull request #4598 from segmentio/jfoskin-patch-2

Tracking Plan implemented

Author: forstisabella

src/protocols/faq.md

@@ -76,10 +76,15 @@ If you [discarded events](/docs/protocols/enforce/schema-configuration) as a par
 
 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. 
 
+### How do Tracking Plans work?
+
+Segment's code uses built-in logic to verify if an event exists in the Tracking Plan. If an event does not exist, it will follow the configuration the [Schema Configuration settings](/docs/protocols/enforce/schema-configuration/) for each source connected to the Tracking Plan.
+
 ### Why are my unplanned properties still getting sent to my destinations even though I've set the dropdown to "Omit Properties"?
 
 Unplanned property omission is only supported for cloud-mode destinations. Unplanned properties will not be omitted when they're sent to device-mode destinations.
 
+
 ## Protocols Validation
 
 ### What is the difference between Violations Emails and the Violations page in the Segment UI?