Skip to content

Commit c641a2d

Browse files
committed
1 more fix
1 parent 92dad44 commit c641a2d

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/protocols/tracking-plan/create.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Each track event in the tracking plan has a separate JSON schema definition to v
8686
#### Common JSON schema
8787
The Tracking Plan also uses a common JSON schema definition that applies to the entire payload of every event sent from sources connected to the tracking plan.
8888

89-
The common JSON schema definition is unique for each tracking plan. An example use of this feature is to validate that all track, identify and page events sent to Segment include a `context.device.advertisingId` property. This validation ensures that every Segment call has a userId, anonymousId, and context object with a nested `"device": { "advertisingId": "e23sfsdf"}` object. To update this in the Tracking Plan, you'll need to add it under the `"global"`: object and upload using the API.
89+
The common JSON schema definition is unique for each tracking plan. An example use of this feature is to validate that all track, identify and page events sent to Segment include a `context.device.advertisingId` property. This validation ensures that every Segment call has a userId, anonymousId, and context object with a nested `"device": { "advertisingId": "e23sfsdf"}` object.
9090

9191
```json
9292
{
@@ -147,6 +147,8 @@ To edit the common JSON schema:
147147
3. Once you've saved and merged your JSON schema changes, go to the **Settings** tab for your source.
148148
4. Click **Schema Configuration** in the navigation and go to the **Advanced Blocking Controls** section to define specific blocking behavior for common JSON schema violations.
149149

150+
To edit the common JSON schema using the Config API, you'll need to add your new JSON schema under the `"global"`: object.
151+
150152
> info ""
151153
> [Negative lookahead regexes (`?!`)](https://www.regular-expressions.info/lookaround.html) aren't supported. This means you can’t use regex to prevent matches with a specific following character or expression. But, you can use `not` in the regex of your JSON schema to generate violations when a property key or value doesn't match the provided regex pattern.
152154

0 commit comments

Comments
 (0)