You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/protocols/tracking-plan/create.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,13 +45,12 @@ To download a Tracking Plan:
45
45
## Delete a Tracking Plan
46
46
47
47
> info "Deleting a Tracking Plan requires Workspace Owner or Tracking Plan Admin permissions"
48
-
> You must have Workspace Owner or Tracking Plan Admin roles to delete a Tracking Plan. For more information about roles in the Segment app, see the [Roles documentation](/docs/segment-app/iam/roles/).
48
+
> You must have Workspace Owner or Tracking Plan Admin roles to delete a Tracking Plan. For more information about roles in Segment, see the [Roles documentation](/docs/segment-app/iam/roles/).
49
49
50
50
To delete a Tracking Plan:
51
51
1. Open the Segment app and click **Protocols**.
52
52
2. On the row of the Tracking Plan you want to delete, open the contextual menu(…) and select **Delete Tracking Plan...**
53
-
3. A toast pops up on the top of the page, with the message: <br/>
54
-
*"Are you sure you want to delete <<TrackingPlanName>>? Once you delete this Tracking Plan, you will not be able to recover it..”*
53
+
3. On the "Delete Tracking Plan" popup, click **Delete**.
55
54
56
55
## Edit a Tracking Plan
57
56
The Tracking Plan editor is organized as a spreadsheet to help you add new events and properties, and edit the relevant fields for each. Like a spreadsheet, you can navigate across cells in a single event with your arrow keys and press enter to edit a cell.
@@ -78,7 +77,7 @@ To add a Track call property:
78
77
2. Click into the row to add the property name and also specify the description, status, data type and permitted values when applicable.
79
78
- You can use your keyboard arrow and enter keys to navigate across the cells, or use your mouse.
80
79
81
-
### Add a track call object or array property
80
+
### Add a Track call object or array property
82
81
Segment supports object and array data types in the Tracking Plan editor. These complex data structures have limited use cases and should be used sparingly as some destinations aren't able to ingest the data structures. To add an object or array:
83
82
1. Create a new property row and set the Data Type to `Object` or `Array`.
84
83
2. Click the **(+)** next to the property name to add key value pairs in the object, or objects to an array of objects.
@@ -88,11 +87,16 @@ You can define which traits you expect to see passed in Identify or Group calls
88
87
89
88
It's best to keep traits optional because Identify and Group are often called and pass only _new or changed_ traits, because Segment's client-side libraries (analytics.js, Swift, Kotlin) cache traits in local storage. See the [Identify Best Practices](/docs/connections/spec/best-practices-identify#when-and-how-often-to-call-identify) to learn more.
90
89
91
-
### Remove a Source from your Tracking Plan
92
-
93
-
90
+
### Remove a source from your Tracking Plan
94
91
92
+
> info "Removing a source from a Tracking Plan requires Workspace Owner or Tracking Plan Admin permissions"
93
+
> You must have Workspace Owner or Tracking Plan Admin roles to remove a source from a Tracking Plan. For more information about roles in Segment, see the [Roles documentation](/docs/segment-app/iam/roles/).
95
94
95
+
To remove a source from your Tracking Plan:
96
+
1. Click **Protocols** in the left navigation bar.
97
+
2. Find the Tracking Plan you'd like to remove a source from, then select the source icon in the Connected Sources column.
98
+
3. On the list of sources connected to your Tracking Plan, find the source you'd like to remove from your Tracking Plan and click **Disconnect**.
99
+
4. Review the "Disconnect source from Tracking Plan" popup and click **Disconnect**.
96
100
97
101
### Add a label
98
102
You can apply `key:value` labels to each event to help organize your Tracking Plan. These labels are helpful when multiple teams are managing a single Tracking Plan, or if you want to specify a priority, platform, product, or similar meta-data for each event. You can filter by label from the Tracking Plan, Schema, Data Validation and Violations Summary views.
0 commit comments