Skip to content

[DOCS-13737] Add API tracking section to Product Analytics landing page#35929

Open
iadjivon wants to merge 12 commits intomasterfrom
ida.adjivon/DOCS-13737-pana-api-link
Open

[DOCS-13737] Add API tracking section to Product Analytics landing page#35929
iadjivon wants to merge 12 commits intomasterfrom
ida.adjivon/DOCS-13737-pana-api-link

Conversation

@iadjivon
Copy link
Copy Markdown
Contributor

@iadjivon iadjivon commented Apr 10, 2026

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:

  • Restructured "Instrument your application" section with two subsections: Client-side tracking (SDK) and Server-side tracking (API)
  • Added intro paragraph framing both methods as complementary data sources
  • Linked to the Product Analytics send events API endpoint
  • Added billing warning for server-side events
  • Reframed coding assistant reference as a distinct setup method linking to Agentic onboarding
  • Broke platform list into bulleted format for readability
  • Converted RUM/retention note to HTML callout

Merge instructions

Merge readiness:

  • Ready for merge

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

@iadjivon iadjivon added the WORK IN PROGRESS No review needed, it's a wip ;) label Apr 10, 2026
@iadjivon iadjivon requested a review from a team as a code owner April 10, 2026 21:14
@iadjivon iadjivon changed the title Ida.adjivon/docs 13737 pana api link [DOCS-13737] Add API tracking section to Product Analytics landing page Apr 10, 2026
@github-actions
Copy link
Copy Markdown
Contributor

Preview links (active after the build_preview check completes)

Modified Files

iadjivon and others added 5 commits April 12, 2026 23:49
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@@ -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**.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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].
Copy link
Copy Markdown
Contributor Author

@iadjivon iadjivon Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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**
Copy link
Copy Markdown
Contributor Author

@iadjivon iadjivon Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE: For this section, Actions, I only removed a trailing space at the end. No other changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants