newrelic · WriteMayur · Dec 4, 2025 · Dec 4, 2025
diff --git a/.../new-relic-browser/browser-pro-features/page-views-examine-page-performance.mdx b/.../new-relic-browser/browser-pro-features/page-views-examine-page-performance.mdx
@@ -4,7 +4,7 @@ tags:
   - Browser
   - Browser monitoring
   - Additional standard features
-metaDescription: "Get actionable data for your single page app or website's performance, timing, throughput, page loads, and more with our Page views UI for browser monitoring."
+metaDescription: "Get actionable data for your single page app or website's performance, timing, throughput, page loads, user frustration signals, and session replays with our Page views UI for browser monitoring."
 redirects:
   - /docs/new-relic-browser/page-views-dashboard
   - /docs/browser/new-relic-browser/dashboard-details/page-views-dashboard
@@ -14,7 +14,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-The <DNT>**Page views**</DNT> page in <InlinePopover type="browser"/> provides insight into the performance of your site's pages. Sort options help you find details about percentage of page load time, average page load time, or throughput. Detailed information about the top webpages viewed, timing and throughput details, and links to browser traces or session traces also are available.
+The <DNT>**Page views**</DNT> page in <InlinePopover type="browser"/> provides insight into the performance of your site's pages and user experience. Sort options help you find details about percentage of page load time, average page load time, or throughput. You can also view user frustration signals and performance impact metrics, access session replays, and explore detailed information about the top webpages viewed.
 
 Our browser capabilities include [single-page app (SPA) monitoring](/docs/browser/single-page-app-monitoring/get-started/welcome-single-page-app-monitoring). If you have opted in to SPA monitoring, your SPA <DNT>**Page views**</DNT> UI will be different. You can toggle between which view (SPA or standard browser) you want.
 
@@ -38,6 +38,62 @@ To view detailed information about which pages the end users are viewing for you
 2. Toggle the page view for SPA or standard browser apps as applicable.
 3. Select the type of view for page load timing information as a [chart (default), histogram, or percentile](/docs/apm/apm-ui-pages/monitoring/response-time-chart-types-apm-browser/).
 
+## Understand user impact metrics [#user-impact-metrics]
+
+The Page views page includes user impact cards that help you understand how performance issues affect your users' experience.
+
+### Frustration signals [#frustration-signals]
+
+The <DNT>**Frustration signals**</DNT> card shows the percentage of user sessions containing frustration indicators in the selected time period. Frustration signals include:
+
+* **Rage clicks**: Users rapidly clicking the same element 4 or more times within 1 second
+* **Dead clicks**: Clicks that don't result in any detectable change within 2 seconds  
+* **Error clicks**: Clicks followed by a JavaScript error within 2 seconds
+
+The card displays:
+* **Percentage of sessions** with frustration signals in the selected time range
+* **Total sessions** and **total replays** available (hover over "View session details" for details)
+* **Analyze frustration signals** link to view detailed analysis in the [User Impact page](/docs/browser/new-relic-browser/browser-pro-features/user-impact)
+
+### Performance impact [#performance-impact]
+
+The <DNT>**Performance impact**</DNT> card shows the percentage of user sessions affected by performance issues in the selected time period. Performance issues include:
+
+* **JavaScript errors**: Unhandled exceptions and application errors
+* **Poor Core Web Vitals**: Failing Largest Contentful Paint (LCP), Interaction to Next Paint (INP), or Cumulative Layout Shift (CLS) thresholds
+
+The card displays:
+* **Percentage of sessions** with performance issues in the selected time range
+* **Total sessions** and **total replays** available (hover over "View session details" for details)
+* **Analyze performance impact** link to view detailed analysis in the [User Impact page](/docs/browser/new-relic-browser/browser-pro-features/user-impact)
+
+### Session Replay sampling considerations [#sampling-considerations]
+
+The user impact cards adapt based on your Session Replay configuration:
+
+<CollapserGroup>
+  <Collapser
+    id="sr-enabled"
+    title="Session Replay enabled with standard sampling"
+  >
+    When Session Replay is enabled with sampling rates at or above default thresholds (10% for general sampling, 100% for error sampling), both cards display full metrics with session replay counts and direct links to replay sessions.
+  </Collapser>
+
+  <Collapser
+    id="sr-low-sampling"
+    title="Session Replay enabled with low sampling"
+  >
+    When sampling rates are below recommended thresholds, the cards display a notice suggesting you increase your sample rate. Click the "Increase your sample rate" link to navigate to your browser application settings.
+  </Collapser>
+
+  <Collapser
+    id="sr-disabled"
+    title="Session Replay disabled"
+  >
+    When Session Replay is disabled, the cards show only session counts without replay data. A notice appears with "See where your users are struggling" and a "Turn on session replays" link to enable the feature.
+  </Collapser>
+</CollapserGroup>
+
 ## Examine performance details [#view_details]
 
 From the page view summary, click a URL to view performance details about page load, frontend and backend timing in [APM](/docs/apm/apm-ui-pages/features/request-queuing-tracking-front-end-time/) or in [distributed tracing](/docs/distributed-tracing/ui-data/understand-use-distributed-tracing-ui), throughput, [types of browsers](/docs/browser/new-relic-browser/additional-standard-features/browsers-problem-patterns-type-or-platform), and [session traces](/docs/browser/browser-monitoring/browser-pro-features/session-traces-explore-webpages-life-cycle).
@@ -53,6 +109,40 @@ From here you can also:
 * Compare page load and throughput performance with yesterday and last week.
 * View response time for app response time for web transactions.
 
+## Access session replays [#session-replays]
+
+The browser interactions table includes a <DNT>**Session replays**</DNT> column that shows the count of available session replays for each page. This integration provides direct access to qualitative user experience data alongside quantitative performance metrics.
+
+### Session replay column features [#session-replay-column]
+
+* **Replay counts**: The Session replays column displays the number of available replays for each browser interaction or transaction
+* **Direct navigation**: Click any session replay count to open the [Session Replay list page](/docs/browser/browser-monitoring/browser-pro-features/session-replay) with relevant filters applied
+* **Context preservation**: Applied filters from the Page views interface carry over to Session Replay, maintaining your analysis context
+* **No data indicator**: Pages without session replays show a dash (`-`) and are not clickable
+
+### Navigate to detailed analysis [#navigate-analysis]
+
+The user impact cards provide multiple ways to explore your data in depth:
+
+* **View session details**: Hover over this link to see a tooltip with total sessions and available replay counts for the selected time range
+* **Analyze frustration signals**: Click to navigate to the User Impact page with the Frustration metrics tab selected and relevant filters applied
+* **Analyze performance impact**: Click to navigate to the User Impact page with the Performance impact tab selected and relevant filters applied
+
+### View session replays [#view-replays]
+
+To access session replays from the Page views table:
+
+1. Locate the <DNT>**Session replays**</DNT> column in the browser interactions table
+2. Click any session replay count to open filtered session replays
+3. The Session Replay page opens with these filters automatically applied:
+   * **Browser interaction name** (for SPA views) or **Browser transaction name** (for standard views)
+   * **Current time range** from your Page views selection
+   * **Additional context filters** based on your Page views configuration
+
+<Callout variant="important">
+  Session replay counts depend on your [Session Replay sampling configuration](/docs/browser/browser-monitoring/browser-pro-features/session-replay#configure-sampling). If you see consistently low or zero counts, consider [increasing your sampling rate](/docs/browser/new-relic-browser/configuration/browser-app-settings-page#session-replay) to capture more user sessions.
+</Callout>
+
 ## Examine timing details for page loads [#page_load_timing]
 
 The [page load timing process](/docs/browser/new-relic-browser/page-load-timing-resources/page-load-timing-process) shows colored-coded details:

diff --git a/src/content/docs/browser/new-relic-browser/browser-pro-features/user-impact.mdx b/src/content/docs/browser/new-relic-browser/browser-pro-features/user-impact.mdx
@@ -0,0 +1,165 @@
+---
+title: 'User impact: Analyze frustration signals and performance impact'
+tags:
+  - Browser
+  - Browser monitoring
+  - Additional standard features
+  - User experience
+  - Session replay
+metaDescription: "Analyze user frustration signals, performance impact, and session replays to understand how technical issues affect your users' experience with New Relic browser monitoring."
+freshnessValidatedDate: never
+---
+
+The <DNT>**User impact**</DNT> page in <InlinePopover type="browser"/> helps you understand how technical performance issues affect your users' actual experience. This page bridges quantitative performance metrics with qualitative user behavior analysis, providing insights into user frustration patterns and their correlation with technical problems.
+
+The User impact page consists of two main analysis areas: <DNT>**Frustration metrics**</DNT> and <DNT>**Performance impact**</DNT>. Each provides different lenses for understanding user experience issues and their technical root causes.
+
+## Access User impact analysis [#access]
+
+To view the User impact page:
+
+1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Browser > (select an app)**</DNT>.
+2. In the left navigation under <DNT>**More views**</DNT>, click <DNT>**User impact**</DNT>.
+3. Select either <DNT>**Frustration metrics**</DNT> or <DNT>**Performance impact**</DNT> from the tab.
+
+You can also navigate here directly from the [Page views](/docs/browser/new-relic-browser/browser-pro-features/page-views-examine-page-performance) page by clicking <DNT>**Analyze frustration signals**</DNT> or <DNT>**Analyze performance impact**</DNT> link.
+
+## Analyze frustration metrics [#frustration-metrics]
+
+The Frustration metrics tab focuses on user behavioral indicators that signal confusion, annoyance, or difficulty completing tasks. This analysis helps you identify where users struggle most and prioritize fixes based on actual user pain points.
+
+### Rage click analysis [#rage-clicks]
+
+Rage clicks occur when users rapidly click the same element multiple times, typically indicating an unresponsive interface or broken functionality.
+
+**Rage click trend chart:**
+
+* Shows overall frustration patterns over time with deployment markers for correlation
+* Helps identify if recent deployments increased user frustration
+* Displays the overall frustration trend across your application
+
+**Top affected pages table:**
+
+* Lists browser interactions (SPA) or browser transactions (standard) with the highest rage click activity
+* Shows total rage clicks, associated errors, and available session replay counts for each page
+* Click session replay counts to view filtered sessions with frustration signals
+* Includes a "View all" option to explore the complete list with search capabilities
+
+**Rage click events chart:**
+
+* Displays a stacked bar chart showing rage click trends for specific pages
+* Use the dropdown to filter by the top affected pages
+* Analyze patterns for individual browser interactions or transactions
+
+### Top affected page elements [#affected-elements]
+
+This section provides granular analysis of which specific UI elements cause the most user frustration:
+
+**Metadata section:**
+* Shows the percentage of rage clicks among total user interactions
+* Provides context for how widespread frustration signals are relative to normal usage
+
+**Elements table:**
+* **Target tag and target class**: Identifies the specific HTML elements users rage-click most frequently
+* **Rage click rate**: Shows the percentage of sessions that included rage clicks on each element
+* **Most affected URLs**: Displays which pages contain the problematic elements
+* **Session replays**: Count of available replays for analysis (click to view filtered sessions)
+* **Recommended sessions**: Direct access to sessions where rage clicks correlate with JavaScript errors
+
+<Callout variant="tip">
+  Recommended sessions prioritize replays where rage clicks immediately follow JavaScript errors, providing the strongest correlation between technical issues and user frustration.
+</Callout>
+
+## Analyze performance impact [#performance-impact]
+
+The Performance impact tab examines how technical performance problems affect user sessions, focusing on measurable performance metrics and their correlation with user experience issues.
+
+### Web vitals monitoring [#web-vitals]
+
+Core Web Vitals provide standardized metrics for user experience quality:
+
+* **Largest Contentful Paint (LCP)**: Loading performance measurement
+* **Interaction to Next Paint (INP)**: Responsiveness to user interactions  
+* **Cumulative Layout Shift (CLS)**: Visual stability during page load
+
+Each metric displays current values with status indicators (good, needs improvement, poor) based on Google's recommended thresholds.
+
+### Error analysis [#error-analysis]
+
+**Error rate trend:**
+* Shows JavaScript error patterns over time with deployment markers
+* Helps correlate error spikes with specific deployments or changes
+* Displays overall error trends across your application
+
+**Error rate distribution:**
+* Provides a breakdown of the most frequently occurring error types
+* Shows error counts faceted by error messages
+* Click specific error types to navigate to detailed error analysis in Error Inbox
+
+### Top affected pages analysis [#affected-pages-performance]
+
+This table identifies which pages experience the most performance-related user impact:
+
+* **Page URL**: Browser interactions (SPA) or browser transactions (standard) with performance issues
+* **Error class and error message**: Specific types of errors occurring on each page
+* **Error rate**: Percentage of sessions affected by errors on each page
+* **Session replays**: Available replay counts for affected sessions
+* **Recommended sessions**: Direct access to sessions with the highest correlation between errors and user impact
+
+Click session replay counts to view sessions filtered by error class and error message, maintaining analysis context.
+
+### Geography analysis [#geography]
+
+Understanding performance impact by geographic location helps identify regional infrastructure or connectivity issues:
+
+**Performance map:**
+* Visual representation of error rates or error counts by geographic region
+* Toggle between error rate (percentage) and error count (absolute numbers) views
+* Zoom functionality to focus on specific regions
+
+**Geography table:**
+* **Location data**: Country, region, or city-level performance breakdown
+* **Error metrics**: Error rates and counts for each geographic area
+* **Session replays**: Available replay counts for geographic segments
+* **Favoriting**: Mark frequently monitored regions for quick access
+* **Filtering**: Click rows to apply geographic filters and zoom the performance map
+
+**Key attributes breakdown:**
+* **Country code and city**: Geographic segmentation options
+* **Browser and browser version**: Technology stack correlation with performance issues
+* **Device type**: Performance differences across device categories
+* **Page URL**: Most problematic pages in each geographic region
+
+<Callout variant="important">
+  Geography analysis requires sufficient data volume to provide meaningful insights. Low-traffic applications may see limited geographic granularity.
+</Callout>
+
+## Navigation and filtering [#navigation-filtering]
+
+### Cross-page workflows [#cross-page]
+
+The User impact page integrates seamlessly with other browser monitoring features:
+
+* **From Page views**: Navigation preserves time ranges and applied filters
+* **To Session Replay**: Session replay counts maintain context with relevant filters applied
+* **To Error Inbox**: Error distribution links carry error type filters
+* **To Browser pages**: Key attributes link to detailed browser analysis
+
+### Filter management [#filter-management]
+
+* **Persistent filters**: Applied filters remain active during page reloads within the same analysis type
+* **Context switching**: Filters reset when switching between Frustration metrics and Performance impact tabs
+* **Dynamic filtering**: Supports device type, page URL, user agent, and geographic filters
+* **Time range synchronization**: Time selections apply consistently across all charts and tables
+
+### Session Replay integration [#session-replay-integration]
+
+Session replay counts throughout the User impact page provide direct access to user sessions:
+
+* **Contextual filtering**: Replays open with relevant filters (rage click events, error conditions, page context)
+* **Recommended prioritization**: "Recommended sessions" highlight replays with the strongest correlation between technical issues and user frustration
+* **Additional context**: Session replay tables include frustration signal counts for each session
+
+<Callout variant="caution">
+  Session replay availability depends on your [sampling configuration](/docs/browser/browser-monitoring/browser-pro-features/session-replay#configure-sampling). Consider increasing sampling rates if you consistently see low replay counts for high-impact issues.
+</Callout>
diff --git a/src/nav/browser.yml b/src/nav/browser.yml
@@ -92,6 +92,8 @@ pages:
         path: /docs/browser/new-relic-browser/guides/guide-to-monitoring-core-web-vitals
       - title: Page views page
         path: /docs/browser/new-relic-browser/browser-pro-features/page-views-examine-page-performance
+      - title: User impact page
+        path: /docs/browser/new-relic-browser/browser-pro-features/user-impact
       - title: AJAX page
         path: /docs/browser/browser-monitoring/browser-pro-features/ajax-page-identify-time-consuming-calls
       - title: Errors (errors inbox)