Skip to content

Commit de13694

Browse files
author
Michaella Schaszberger
committed
add info sections clarifying the .$ operator
1 parent 00e0576 commit de13694

File tree

2 files changed

+9
-0
lines changed

2 files changed

+9
-0
lines changed

src/connections/sources/schema/index.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,11 @@ The Schema shows "Page Viewed" for all Page calls under the **Track** tab.
2525

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

28+
> 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.
32+
2833
## Event filters
2934

3035
If you no longer want to track a specific event, you can either remove it from your code or, if you're on the Business plan and don't have a Tracking Plan connected, you can block track calls from the Segment UI. To do so, click on the Schema tab in a Source and toggle the event to enable or block an event.

src/protocols/tracking-plan/create.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,10 @@ Segment supports object and array data types in the Tracking Plan editor. These
128128
1. Create a new property row and set the Data Type to `Object` or `Array`.
129129
2. Click the **(+)** next to the property name to add key value pairs in the object, or objects to an array of objects.
130130

131+
> info ""
132+
> When creating array properties, add the `items` nested property to ensure that the items nested property,
133+
> denoted by the name of the array property with a `.$` suffix is marked as planned in the source schema.
134+
131135
### Add Identify or Group traits
132136
You can define which traits you expect to see passed in Identify or Group calls like how you would add Track calls to the Tracking Plan. Navigate to the **Identify** or **Group** tab in your Tracking Plan and click the **(+)** button to add a new trait.
133137

0 commit comments

Comments
 (0)