[DOCS-14641] Add guide page for tracking server-side events in Product Analytics (#37625)

* [DOCS-14641] Add guide page for tracking server-side events in Product Analytics

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Simplify sentence on line 34, remove em dashes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* sent cap

* Apply suggestions from code review

Co-authored-by: Alicia Thuerk <alicia.thuerk@datadoghq.com>

* move to data collected

* update page weight

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Alicia Thuerk <alicia.thuerk@datadoghq.com>

Author: 3 people

config/_default/menus/main.en.yaml

@@ -9740,6 +9740,11 @@ menu:
       parent: product_analytics
       identifier: pa_data_collected
       weight: 6
+    - name: Server-Side Events
+      url: product_analytics/data_collected/server_side_events
+      parent: pa_data_collected
+      identifier: pa_data_collected_server_side_events
+      weight: 601
     - name: Experiments
       url: experiments/
       pre: experiment-wui

content/en/product_analytics/_index.md

@@ -58,7 +58,7 @@ To set up your application with a coding assistant, see [Agentic onboarding][17]
 
 ### Track server-side events (API)
 
-After you set up client-side collection, you can use the [Product Analytics API][21] to send custom events from your server, such as completed checkouts or processed payments.
+After you set up client-side collection, you can use the [Product Analytics API][21] to send custom events from your server, such as completed checkouts or processed payments. For more information, see [Track Server-Side Events][22].
 
 <div class="alert alert-warning">Datadog bills server-side events separately. See the <a href="https://www.datadoghq.com/pricing/?product=product-analytics#products">pricing page</a> for details, and contact your Customer Success Manager with additional questions.</div>
 
@@ -177,3 +177,4 @@ Use the following features to inform your product change decisions, such as chan
 [19]: /real_user_monitoring/guide/understanding-the-rum-event-hierarchy
 [20]: https://app.datadoghq.com/rum/sessions?query=%40type%3Aaction
 [21]: /api/latest/product-analytics/#send-server-side-events
+[22]: /product_analytics/data_collected/server_side_events/

…t/en/product_analytics/data_collected.md …oduct_analytics/data_collected/_index.mdcontent/en/product_analytics/data_collected.md renamed to content/en/product_analytics/data_collected/_index.md content/en/product_analytics/data_collected.md renamed to content/en/product_analytics/data_collected/_index.md

@@ -11,6 +11,9 @@ further_reading:
 - link: "/real_user_monitoring/application_monitoring/android/data_collected/"
   tag: "Documentation"
   text: "RUM Android Data Collected"
+- link: "/product_analytics/data_collected/server_side_events/"
+  tag: "Documentation"
+  text: "Track Server-Side Events"
 ---
 
 ## Overview

content/en/product_analytics/data_collected/server_side_events.md

@@ -0,0 +1,48 @@
+---
+title: Track Server-Side Events
+description: Send custom events from your server to supplement client-side data in Product Analytics.
+further_reading:
+- link: "/api/latest/product-analytics/#send-server-side-events"
+  tag: "API Reference"
+  text: "Product Analytics API"
+- link: "/product_analytics/"
+  tag: "Documentation"
+  text: "Product Analytics"
+- link: "/product_analytics/data_collected/"
+  tag: "Documentation"
+  text: "Product Analytics Data Collected"
+---
+
+## Overview
+
+Server-side events are custom events sent through the [Product Analytics API][1] from your server. Unlike client-side events captured by the RUM SDK, such as pageviews or button clicks, server-side events track actions that occur in your backend, such as a completed checkout or processed payment.
+
+Use server-side events to:
+
+- Capture events at the source of truth on the server, independent of client-side behavior
+- Track backend actions with no client-side equivalent, such as a payment confirmation or subscription renewal
+- Supplement client-side data with server-side context
+
+<div class="alert alert-warning">Datadog bills server-side events separately. See the <a href="https://www.datadoghq.com/pricing/?product=product-analytics#products">pricing page</a> for details, and contact your Customer Success Manager with additional questions.</div>
+
+## Prerequisites
+
+Before sending server-side events, [set up the Datadog SDK][2] for your application and [enable Product Analytics][3].
+
+## Send server-side events
+
+Use the [Product Analytics API][1] to send events from your server. To associate a server-side event with a client session, include the `session_id` from the client's active RUM session. Including the session ID links server-side events to client-side data for a complete view of the user journey.
+
+For the full API reference, including authentication, required fields, and request parameters, see [Send server-side events][1].
+
+## Analyze server-side events
+
+After you send server-side events, they are available in any Product Analytics chart. In the event picker, select **Server Events** to scope your analysis to server-side data.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /api/latest/product-analytics/#send-server-side-events
+[2]: /product_analytics/#track-client-side-events-sdk
+[3]: /product_analytics/#enable-product-analytics

content/en/product_analytics/guide/_index.md

@@ -11,6 +11,7 @@ cascade:
 
 {{< whatsnext desc="General Product Analytics:" >}}
     {{< nextlink href="product_analytics/guide/rum_and_product_analytics" >}}Understanding RUM and Product Analytics{{< /nextlink >}}
+    {{< nextlink href="product_analytics/data_collected/server_side_events" >}}Track server-side events{{< /nextlink >}}
     {{< nextlink href="session_replay/guide/diagnose-funnel-drop-offs-with-session-replay" >}}Diagnose funnel drop-offs with Session Replay{{< /nextlink >}}
     {{< nextlink href="product_analytics/guide/monitor-utm-campaigns-in-product-analytics" >}}Monitor UTM Campaigns{{< /nextlink >}}