Skip to content

Commit 79440d0

Browse files
Apply suggestions from code review
1 parent 9a90f27 commit 79440d0

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

src/protocols/faq.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -87,13 +87,14 @@ Unplanned property omission is only supported for cloud-mode destinations. Unpla
8787

8888
### Why do I have two different Tracking Plan IDs?
8989

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/).
9191

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**.
9393

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`.
9597

96-
*Please be aware that the way you access your Tracking Plan determines the slug that is present in the URL.*
9798

9899
### How do I import events from a Source Schema into a Tracking Plan?
99100

0 commit comments

Comments
 (0)