Skip to content

Commit f060316

Browse files
Update src/connections/sources/schema/index.md
Co-authored-by: forstisabella <[email protected]>
1 parent de13694 commit f060316

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

src/connections/sources/schema/index.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,8 @@ The Schema shows "Page Viewed" for all Page calls under the **Track** tab.
2626
The Source Schema UI changes slightly depending on whether you have a [Protocols Tracking Plan](https://segment.com/docs/protocols/tracking-plan/create/){:target='_blank’} connected to the source. If you have a Tracking Plan connected to your source, the UI displays a **Planned** column that will indicate if the event is planned or unplanned. This allows you to quickly identify unplanned events and take action to align your schema with your Tracking Plan. If there is no Tracking Plan connected to the source, the UI will display a toggle next to each event where, if you're a Business Tier customer, you can simply block or allow that event at the source level.
2727

2828
> info ""
29-
> Array properties will be represented with an additional nested property representing the array's items. This property is the property's name with a `.$` suffix.
30-
> If an array property in the connected tracking plan does not include the `items` nested property, the nested property
31-
> may be marked as unplanned in the source schema.
29+
> Array properties are represented with an additional nested property representing the array's items. The nested property is the property's name with a `.$` suffix.
30+
> If an array property in the connected Tracking Plan does not include the `items` nested property, nested properties might be marked as unplanned in the Source Schema.
3231
3332
## Event filters
3433

0 commit comments

Comments
 (0)