Skip to content

Commit 182df8f

Browse files
authored
Update faq.md
1 parent fd63e78 commit 182df8f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/protocols/faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,9 +76,9 @@ If you [discarded events](/docs/protocols/enforce/schema-configuration) as a par
7676

7777
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.
7878

79-
## How is the Track Plan implemented?
79+
## How does Tracking Plans work behind the scenes?
8080

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.
8282

8383
## Protocols Validation
8484

0 commit comments

Comments
 (0)