From 9df0ae0c146e2df04c5a3d2f68e3c0c81fc99e43 Mon Sep 17 00:00:00 2001 From: Jazma Foskin <82051355+jfoskin@users.noreply.github.com> Date: Fri, 31 May 2024 15:42:50 -0400 Subject: [PATCH 1/2] Schema validated against version 1 of Tracking Plan faq.md --- src/protocols/faq.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/protocols/faq.md b/src/protocols/faq.md index 314f620723..74f1c53a26 100644 --- a/src/protocols/faq.md +++ b/src/protocols/faq.md @@ -154,6 +154,11 @@ Segment's [Schema Controls](docs/connections/sources/schema/destination-data-con 2. **Standard Schema Controls/"JSON Schema Violations"**: Segment checks the names and evaluates the values of properties/traits. This is useful if you've specified a pattern or a list of acceptable values in the [JSON schema](/docs/protocols/tracking-plan/create/#edit-underlying-json-schema) for each Track event listed in the Tracking Plan. 3. **Advanced Blocking Controls/"Common JSON Schema Violations"**: Segment evaluates incoming events thoroughly, including event names, context field names and values, and the names and values of properties/traits, against the [Common JSON schema](/docs/protocols/tracking-plan/create/#common-json-schema) in your Tracking Plan. + +### Why am I still seeing unplanned properties within the source Schema, when the properties have been added to newer versions of the Tracking Plan? + +The schema will only validate events against the oldest event version that exists in the tracking plan, so if you have version 1 and version 2, the schema page will only check the tracking plan against version 1. + ### Do blocked and discarded events count towards my MTU counts? Blocking events within a [Source Schema](/docs/connections/sources/schema/) or [Tracking Plan](/docs/protocols/tracking-plan/create/) excludes them from API call and MTU calculations, as the events are discarded before they reach the pipeline that Segment uses for calculations. From 97dfefbaa6ae78780b902fad48ec11dd93cdb475 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 1 Oct 2024 11:22:06 -0400 Subject: [PATCH 2/2] Apply suggestions from code review --- src/protocols/faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/protocols/faq.md b/src/protocols/faq.md index 74f1c53a26..9b7d47a30e 100644 --- a/src/protocols/faq.md +++ b/src/protocols/faq.md @@ -155,9 +155,9 @@ Segment's [Schema Controls](docs/connections/sources/schema/destination-data-con 3. **Advanced Blocking Controls/"Common JSON Schema Violations"**: Segment evaluates incoming events thoroughly, including event names, context field names and values, and the names and values of properties/traits, against the [Common JSON schema](/docs/protocols/tracking-plan/create/#common-json-schema) in your Tracking Plan. -### Why am I still seeing unplanned properties within the source Schema, when the properties have been added to newer versions of the Tracking Plan? +### Why am I still seeing unplanned properties in my Source Schema when I've added the properties to a new version of my Tracking Plan? -The schema will only validate events against the oldest event version that exists in the tracking plan, so if you have version 1 and version 2, the schema page will only check the tracking plan against version 1. +The source schema only validates events against the oldest event version in a Tracking Plan. If, for example, you have a version 1 and version 2 of your Tracking Plan, the schema only checks against version 1 of your Tracking Plan. ### Do blocked and discarded events count towards my MTU counts?