Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ on omitted properties #7190

Merged
merged 2 commits into from
Dec 17, 2024
Merged

Add FAQ on omitted properties #7190

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bcb7dac
Add FAQ on omitted properties
ashton-huxtable Oct 31, 2024
941a536
Update src/protocols/faq.md
forstisabella Dec 17, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions src/protocols/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,10 @@ That being said, there are plenty of scenarios where the reactive Schema functio

Blocked events are blocked from sending to all Segment Destinations, including warehouses and streaming Destinations. When an Event is blocked using a Tracking Plan, it does not count towards your MTU limit. They will, however, count toward your MTU limit if you enable [blocked event forwarding](/docs/protocols/enforce/forward-blocked-events/) in your Source settings.

### If I omit unplanned properties or properties that generate JSON schema violations, what happens to them?

Properties that are omitted due to JSON Schema Violations or being unplanned are not stored in Segment logs. Segment only stores fully blocked events for 30 days. Omitted properties are dropped from the events and can only be found in the `context.violations` object of an event payload. If Violations are forwarded to a new source, then the omitted properties can also be seen in the Violation Generated event under `violationField` in the `properties` object of the event.
forstisabella marked this conversation as resolved.
Show resolved Hide resolved

### Why am I seeing unplanned properties/traits in the payload when violations are triggered, despite using schema controls to omit them?

If you're seeing unplanned properties/traits in your payload despite using Schema Controls, you might want to select a new degree of blocking controls.
Expand Down