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.

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 details on blocking data using JSON Schema #5522

Merged
merged 2 commits into from
Oct 12, 2023
Merged
Changes from 1 commit
Commits
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
3 changes: 3 additions & 0 deletions src/protocols/tracking-plan/create.md
Original file line number Diff line number Diff line change
Expand Up @@ -174,6 +174,9 @@ To edit the common JSON schema using the Public API, you'll need to add your new
> info "Specifying data type"
> Property or trait data type should adhere to the [data types defined by JSON schema](https://json-schema.org/understanding-json-schema/reference/type.html){:target="_blank”}. Data type names must be lower-cased as specified in JSON schema. Datetime properties should be represented as a `string` type with [`format` keyword](https://json-schema.org/understanding-json-schema/reference/string.html#format){:target="_blank”} (for example: "format": "date-time").

> info "Blocking data"
> JSON schema violation event blocking is ONLY supported in cloud-mode Destinations. See [here](https://segment.com/docs/protocols/enforce/schema-configuration/){:target="_blank”} for more information on blocking data.
forstisabella marked this conversation as resolved.
Show resolved Hide resolved

### Extend the Tracking Plan
Some customers prefer to manage the Tracking Plan with outside tools and resources. See the [APIs and extensions](/docs/protocols/apis-and-extensions/) section to learn more.

Expand Down