[DOCS-13737] Add API tracking section to Product Analytics landing page#35929
[DOCS-13737] Add API tracking section to Product Analytics landing page#35929
Conversation
Preview links (active after the
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ction of the page.
| @@ -57,6 +76,9 @@ Product Analytics is built on three levels of user data RUM collects: Sessions, | |||
| **Actions** | |||
| : An action is something a user does on a page, such as a click, tap, or scroll. Actions are automatically collected by the RUM SDK. When configuring features like [Funnels][4] and [Segments][6], you can select specific Actions as steps or filters. To see which Actions are available, open the [RUM Explorer][20] and filter by **Actions**. | |||
|
|
|||
There was a problem hiding this comment.
Note: "Server-side events" is used as the definition term for consistency with the rest of the page. The bold Server Events in the body matches the UI label in the event picker.
|
|
||
| ## Understand your data | ||
| Product Analytics is built on three levels of user data RUM collects: Sessions, Views, and Actions. For a full breakdown of RUM event types, see [Understanding the RUM Event Hierarchy][19]. | ||
| Product Analytics collects client-side and server-side event data. For client-side data, Product Analytics uses three levels of RUM data: Sessions, Views, and Actions. For a full breakdown of RUM event types, see [Understanding the RUM Event Hierarchy][19]. |
There was a problem hiding this comment.
NOTE: I did not include anything about the server side in the intro here on purpose. I only mention that it is collected.
I clarified the levels of RUM data for client-side since RUM collects more than 3 events and PA only uses those 3.
Adding context about the server-side here might add additional context that would duplicate what is already mentioned under Server-side events.
Let me know if it'd be better to include additional context for server-side as well.
| @@ -55,7 +74,10 @@ Product Analytics is built on three levels of user data RUM collects: Sessions, | |||
| : A view represents each page or screen a user visits within a session. | |||
|
|
|||
| **Actions** | |||
There was a problem hiding this comment.
NOTE: For this section, Actions, I only removed a trailing space at the end. No other changes.
What does this PR do? What is the motivation?
Fixes DOCS-13737
Adds server-side API tracking as a first-class instrumentation method on the Product Analytics landing page. Changes include:
Merge instructions
Merge readiness:
Additional notes
This page is in line to be revamped with new UI changes. Please note the scope of this page is to add the server-side information