Commit2654225

authored

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

Tracking Plan implemented

2 parentsa2fefa4 +beac220 commit2654225Copy full SHA for 2654225

File tree

-0

lines changed

-0

lines changed

Lines changed: 5 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -76,10 +76,15 @@ 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 do Tracking Plans work?`
	`80`	`+`
	`81`	`+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.`
	`82`	`+`
`79`	`83`	`###Why are my unplanned properties still getting sent to my destinations even though I've set the dropdown to "Omit Properties"?`
`80`	`84`
`81`	`85`	`Unplanned property omission is only supported for cloud-mode destinations. Unplanned properties will not be omitted when they're sent to device-mode destinations.`
`82`	`86`
	`87`	`+`
`83`	`88`	`##Protocols Validation`
`84`	`89`
`85`	`90`	`###What is the difference between Violations Emails and the Violations page in the Segment UI?`

Comments

(0)