> ## Documentation Index
> Fetch the complete documentation index at: https://docs.germainux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User Click Analysis for Salesforce Cloud (Configure)

> GermainUX captures Salesforce user clicks as individual KPIs, letting teams measure adoption, responsiveness, and productivity for each interaction.

Components
[`Engine`](https://docs.germainux.com/main/germain-ux-engine)
[`JS Profiler`](https://docs.germainux.com/main/germain-ux-js-profiler)
[`Mobile App`](https://docs.germainux.com/main/germain-ux-mobile-app)
[`RPA Bot Recorder`](https://docs.germainux.com/main/germain-ux-rpa-bot-recorder)
[`RUM Ext`](https://docs.germainux.com/main/germain-ux-rum-extension)
[`RUM JS`](https://docs.germainux.com/main/germain-ux-rum-js)

Availability
2017.1 or later

> [card] [Correlated events](#correlated-events)
>
> Link clicks to slow causes

> [card] [Measure Click Response Time](#measure-click-response-time)
>
> Percentiles reveal hidden slowness

> [card] [View User Click Data](#view-user-click-data)
>
> Find clicks in Workspace

> [card] [Too Many Clicks Are Collected](#too-many-clicks-are-collected)
>
> Reduce noisy click collection

## Overview

GermainUX captures and analyzes Salesforce user clicks as individual KPIs, allowing teams to measure adoption, responsiveness, productivity, and technical activity associated with each interaction.

## Correlated events

A Salesforce User Click can be correlated with:

* JavaScript execution
* Browser errors
* Network requests
* Salesforce Aura calls
* Apex execution
* SOQL queries

> [accordion] Show all 11
>
> * Database activity
> * API and integration calls
> * User-facing errors
> * Business-process steps
> * Session Replay

This helps teams move from “the user clicked a button” to “the interaction was slow or failed because of this browser, Salesforce, Apex, database, or integration activity.”

> [!NOTE]
>
> Salesforce User Click is a distinct KPI. It complements Session Replay but does not replace it.

## User Click KPI vs. Session Replay

| Capability | Salesforce User Click | Session Replay |
| - | - | - |
| Measures an individual interaction | Yes | Provides the surrounding visual sequence |
| Calculates response duration | Yes | Shows how the wait appeared to the user |
| Supports aggregation across users | Yes | Primarily used for instance-level investigation |
| Supports averages and percentiles | Yes | No |
| Supports adoption and usage counts | Yes | Not its primary purpose |
| Correlates with technical calls | Yes | Displays correlated evidence for the session |
| Shows what the user saw | Limited to captured metadata | Yes |
| Helps reproduce an issue | Provides the exact action and related trace | Provides the complete sequence and UI context |

Use User Click KPIs to identify and prioritize patterns at scale. Open Session Replay to understand an individual occurrence.

## Raw Clicks vs. Business-Meaningful Clicks

Not every browser click has business value.

| Click type | Description | Example |
| - | - | - |
| **Raw click** | Any detected mouse click in the Salesforce UI | Clicking a tab, icon, blank area, or control |
| **Business-meaningful click** | A named action relevant to adoption, productivity, conversion, or workflow analysis | Save Case, Submit Approval, Convert Lead |
| **Workflow step** | An interaction used to mark progression through a defined process | Opportunity moved to the next stage |
| **Error-related click** | An interaction associated with a failure or unsuccessful result | Save followed by an error toast |
| **Repeated or frustrated click** | Multiple clicks indicating delay or unclear UI feedback | Repeatedly clicking Submit |

Configure meaningful names and context so dashboards report understandable actions instead of unstable HTML or framework details.

## Prerequisites

Before configuring Salesforce User Click Analysis:

* Complete [Salesforce Monitoring Deployment](https://docs.germainux.com/main/salesforce-monitoring-deployment.md).
* Deploy the GermainUX RUM Extension to the intended Salesforce users.
* Configure the Salesforce application and UX Monitoring Profile.
* Confirm that browsers can send data to GermainUX.
* Configure Salesforce CSP Trusted Sites.
* Apply masking, anonymization, and exclusion rules.
* Enable Engine-based Salesforce monitoring if backend correlation is required.

For the broader RUM configuration, see [Salesforce User Monitoring and Session Replay](https://docs.germainux.com/main/salesforce-user-monitoring-and-replay.md).

## Select the Monitoring Method

| Salesforce context | Recommended method |
| - | - |
| **Salesforce Lightning** | RUM Extension |
| **Salesforce Classic** | RUM Extension |
| **A controlled custom page where JavaScript can be injected** | RUM JS may be used if technically and organizationally supported |
| **Complete Salesforce page monitoring** | RUM Extension |

A custom Aura or Lightning component cannot independently monitor the complete Salesforce root page because Salesforce security isolates component code. Use the RUM Extension when complete user-interaction coverage is required.

## Configure the Salesforce UX Monitoring Profile

In GermainUX Workspace, navigate to:

Analytics
UX Monitoring Profiles
Salesforce

The profile determines how GermainUX:

* Detects Salesforce clicks
* Identifies the clicked control
* Assigns an action name
* Captures the active page and component
* Measures response duration
* Enriches the click with Salesforce context
* Processes related network activity
* Correlates the click with other facts

Use the current Salesforce profile supplied for your GermainUX version.

## Configure Click Naming

A click name should describe the user’s action in language understood by Salesforce administrators, product owners, and business teams.

Good names include:

* `Click on Save Case`
* `Click on Submit for Approval`
* `Click on Convert Lead`
* `Click on New Opportunity`
* `Click on Search`
* `Click on Add Product`
* `Click on Next`
* `Click on Close Case`

Avoid names based only on:

* Generated CSS classes
* Dynamic DOM IDs
* Framework-internal component names
* Icon filenames
* Element positions
* Unstable Salesforce implementation details

A reliable naming strategy may use:

* Visible button or link text
* Accessible label
* `aria-label`
* Salesforce component metadata
* Stable attributes
* Parent or neighboring label
* A custom mapping for critical actions

## Capture Click Context

Enrich each click with the available context needed for analysis.

Recommended attributes include:

| Attribute | Purpose |
| - | - |
| **Application** | Identifies Salesforce or a Salesforce application |
| **Page or view** | Identifies where the action occurred |
| **Salesforce component** | Identifies the relevant Lightning or Classic component |
| **Action name** | Describes what the user clicked |
| **User** | Supports user-level analysis, subject to privacy policy |
| **Profile or role** | Supports segmentation by user group |
| **Salesforce organization** | Distinguishes monitored organizations |
| **Environment** | Separates production, staging, and test |
| **Business object** | Identifies the relevant object type or anonymized record |
| **Business-process step** | Connects the click to a workflow |
| **Session ID** | Correlates the click with the user session |
| **Correlation ID** | Connects browser and backend telemetry |
| **Result or status** | Identifies success or failure |
| **Duration** | Measures the response time following the click |

Do not capture raw Salesforce record IDs, customer data, or other sensitive values unless required and approved.

## Measure Click Response Time

GermainUX measures the duration of supported Salesforce interactions so teams can analyze:

* Average response time
* Median response time
* p75, p90, p95, or p99
* Maximum duration
* SLA compliance
* Trends over time
* Differences by user, browser, location, application, or action

Percentiles are especially important because averages can conceal a smaller group of users experiencing severe delays.

![User Click Analysis for Salesforce Cloud (Configure): Measure Click Response Time](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-214843.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=ba03e2c63da638818fb522f56c7f9656)

## Correlate Clicks With Technology Activity

When the appropriate sources are configured, a Salesforce User Click can be correlated with events such as:

* JavaScript execution
* JavaScript console errors
* Browser freezes
* HTTP requests
* Aura requests
* API calls

> [accordion] Show all 11
>
> * Apex classes and triggers
> * SOQL queries
> * Database operations
> * Server-side exceptions
> * Integration calls

![User Click Analysis for Salesforce Cloud (Configure): Correlate Clicks With Technology Activity](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-215901.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=afabe625b300c857e0b8d3d0142679cd)

This correlation helps determine whether a slow or failed interaction originated in:

* The browser
* Salesforce Lightning
* Custom code
* Apex
* A query
* Salesforce infrastructure
* A connected service
* The user’s network or device

![User Click Analysis for Salesforce Cloud (Configure): Correlate Clicks With Technology Activity, image 2](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-220508.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=73f9a255d05ab15d920680f444214283)

## Configure Important Business Actions

Start with actions that directly affect adoption, productivity, or critical workflows.

![User Click Analysis for Salesforce Cloud (Configure): Configure Important Business Actions](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-221015.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=03067a2d8da903a7116157b9e2c6b84b)

### Service and Case Management

* Create Case
* Save Case
* Assign Case
* Escalate Case
* Close Case
* Search Customer
* Add Case Comment

### Sales

* Create Lead
* Convert Lead
* Create Opportunity
* Update Opportunity
* Add Product
* Submit Quote
* Submit for Approval
* Close Opportunity

### General Salesforce Usage

* Open Record
* Edit
* Save
* Cancel
* Search
* Next

> [accordion] Show all 10
>
> * Back
> * Submit
> * Delete
> * Export

Do not configure every possible click initially. Begin with critical actions, validate the data quality, and expand based on business priorities.

## Configure Business-Process Correlation

User clicks can define or enrich Salesforce workflow steps.

For example:

```text theme={null}
Open Case
→ Edit Case
→ Search Customer
→ Update Details
→ Save Case
→ Close Case
```

GermainUX can use the resulting events to identify:

* Step duration
* End-to-end workflow duration
* Drop-offs
* Repeated steps
* Unexpected paths
* Process overruns

> [accordion] Show all 9
>
> * Lost productivity
> * Differences between user groups
> * Technical problems affecting specific steps

![User Click Analysis for Salesforce Cloud (Configure): Configure Business-Process Correlation](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-220111.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=ade3b236d8d81b87a7160d830d45cc03)

See [Business Process and Workflow Monitoring](https://docs.germainux.com/main/business-process-workflow-monitoring.md).

## Configure Success and Failure

Where possible, determine whether a click achieved its intended outcome.

A click may be considered unsuccessful when followed by:

* A Salesforce error toast
* An application error
* An Apex exception
* A failed HTTP request
* An expected page or state not appearing
* A repeated click
* Workflow abandonment
* An excessive response time

Success and failure context makes click counts more useful. High usage does not imply successful usage.

## Configure Adoption Analysis

User Click data can measure:

* Feature adoption
* Usage frequency
* Active users
* New versus returning users
* Adoption by profile, role, or business unit
* Underused functionality

> [accordion] Show all 9
>
> * Workflow completion
> * Training opportunities
> * Changes following a Salesforce release

For example, compare:

* Users who adopted a new Salesforce feature
* Users who still use an older workflow
* Response time for each approach
* Error rate
* Completion time
* Business outcomes

## Configure Privacy

Click metadata can expose:

* User identity
* Record identifiers
* Customer or patient names
* Search terms
* Form values
* Business-object details
* Error messages

Before production rollout:

* Anonymize user identities where required.
* Exclude sensitive record identifiers.
* Mask search terms or field values.
* Avoid using private data in click names.
* Review request and response-body collection.
* Restrict access to user-level analytics and Session Replay.
* Apply appropriate retention.

## Salesforce Click KPIs

See Salesforce Click KPIs.

Relevant measures can include:

* Click count
* Unique users
* Unique sessions
* Average duration
* Percentile duration
* Maximum duration

> [accordion] Show all 10
>
> * Error count
> * Failure rate
> * SLA violation count
> * Total lost-productivity time

Useful pivots include:

* Click name
* Salesforce application
* Page or view
* Component
* User
* Profile

> [accordion] Show all 15
>
> * Role
> * Business unit
> * Browser
> * Location
> * Business process
> * Business-process step
> * Result
> * Error category
> * Environment

## View User Click Data

In GermainUX Workspace:

**1. Open Dashboards**

**2. Select All**

**3. Search for: `Salesforce User Click `**

**4. Open the applicable portlet or KPI**

**5. Select a click name to drill into its instances**

**6. Open an instance to review related events and Session Replay**

## Recommended Dashboard Views

Create views that answer specific questions.

### Adoption

* Most and least used actions
* Unique users by action
* Adoption by team or profile
* Usage before and after a release

### Performance

* Slowest actions
* p95 response time by action
* SLA violations
* Degradation by browser, location, or application version

![User Click Analysis for Salesforce Cloud (Configure): Performance](https://mintcdn.com/germain-ux/BTxCucYnGj_ffpsA/images/main/salesforce-user-click-analysis/image-20260827-215328.png?fit=max\&auto=format\&n=BTxCucYnGj_ffpsA\&q=85\&s=1b22ae48005b6a886c96332e725b1217)

### Insights for DX or UX

* Time spent on high-volume actions
* Repeated or unnecessary interactions
* Workflow overruns
* Total lost productivity

## Validate User Click Monitoring

Test representative Salesforce actions after configuration.

For each action, verify that:

* One click fact is generated.
* The click has a meaningful name.
* The correct application and page are assigned.
* User and session context are present.
* Duration is reasonable.
* Related HTTP or Aura activity is correlated.

> [accordion] Show all 11
>
> * Backend evidence appears when configured.
> * Errors are attached to unsuccessful interactions.
> * Session Replay opens at the relevant moment.
> * Sensitive values are masked or excluded.
> * Repeated clicks are not incorrectly counted as separate business actions unless intended.

Test multiple Salesforce layouts, profiles, browsers, and record types because the underlying UI structure may vary.

## Clicks Are Missing

If expected clicks do not appear:

**1. Confirm that the RUM Extension is installed and enabled**

**2. Confirm that the Salesforce website and profile are configured**

**3. Verify Salesforce CSP Trusted Sites**

**4. Confirm browser connectivity to GermainUX**

**5. Check that the Salesforce UX Monitoring Profile is active**

**6. Inspect the clicked control’s text, accessible label, and stable attributes**

**7. Confirm that the control is not inside an unmonitored context**

**8. Review inclusion and exclusion rules**

**9. Check the selected dashboard time range and environment**

**10. Compare behavior across Salesforce profiles and browsers**

## Click Names Are Incorrect or Unstable

If the same action appears under multiple names:

* Normalize capitalization and whitespace.
* Remove dynamic record values.
* Avoid generated identifiers.
* Prefer visible or accessible labels.
* Add Salesforce-specific mappings.
* Group equivalent names through categorization.
* Test across Salesforce layouts and user profiles.

## Click Durations Are Incorrect

If interaction duration appears too short or too long:

* Confirm which completion event closes the interaction.
* Check for asynchronous Salesforce updates.
* Review related Aura and HTTP calls.
* Identify background calls unrelated to the click.
* Confirm that repeated clicks do not overlap.
* Compare the measurement with Session Replay.
* Review the Salesforce UX profile’s event-processing logic.

## Too Many Clicks Are Collected

If raw activity creates excessive noise:

* Focus on business-meaningful selectors.
* Exclude decorative or low-value controls.
* Aggregate repeated UI patterns.
* Separate raw click heatmaps from business-action KPIs.
* Retain only the context required for analysis.
* Prioritize actions tied to critical Salesforce workflows.

## Related Documentation

> [card] [Dashboard & Reports](https://docs.germainux.com/main/dashboard-and-report.md)
>
> Dashboard & Reports

> [card] [AI](https://docs.germainux.com/main/ai-driven-insights.md)
>
> Insights & Recommendations

> [card] [Analytics](https://docs.germainux.com/main/analytics.md)
>
> More Analytics Features

> [card] [Automation](https://docs.germainux.com/main/automation.md)
>
> More Automation Features

## Get Help

> [card] [Contact GermainUX Support](https://docs.germainux.com/main/support.md)
>
> The GermainUX team helps you get up and running faster, empower your team, turn data into actionable insights, and optimize performance to deliver measurable business outcomes.

> [card] Can't find what you need?
>
> Search all GermainUX docs with **Ctrl + K**, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.