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/faq.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,13 +87,14 @@ Unplanned property omission is only supported for cloud-mode destinations. Unpla
87
87
88
88
### Why do I have two different Tracking Plan IDs?
89
89
90
-
When you access a Tracking Plan, you'll come across two IDs: `tp_` and `rs_`.
90
+
When you access a Tracking Plan, you'll come across two IDs: `tp_` and `rs_`. Segment uses the two IDs to identify your Tracking Plan in the two APIs you can use to manage your workspace: the [Public API](/docs/api/public-api/) and the [Config API](/docs/api/config-api/).
91
91
92
-
If you are using Public API, copy the ID that starts with "tp".
92
+
To view the two IDs for your Tracking Plan, navigate to the Tracking Plan you'd like to view the ID for and select the dropdown next to **Tracking Plan ID**.
93
93
94
-
If you are using Config API, copy the ID that starts with "rs".
94
+
If you're using the Public API, you'll need the ID that starts with `tp_`.
95
+
96
+
If you're using the Config API, you'll need the ID that starts with `rs`.
95
97
96
-
*Please be aware that the way you access your Tracking Plan determines the slug that is present in the URL.*
97
98
98
99
### How do I import events from a Source Schema into a Tracking Plan?
0 commit comments