Skip to content

Commit fd63e78

Browse files
authored
Tracking Plan implememneted
1 parent f6f522f commit fd63e78

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/protocols/faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,10 @@ 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?
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.
82+
7983
## Protocols Validation
8084

8185
### What is the difference between Violations Emails and the Violations page in the Segment UI?

0 commit comments

Comments
 (0)