From 2ec4563c2c5de95ea1d0a48de71022c39d5a149c Mon Sep 17 00:00:00 2001 From: "beltran.bulbarella" Date: Fri, 10 Jul 2026 12:10:55 +0200 Subject: [PATCH 1/3] add Salesforce LWC docs --- rum_salesforce_lwc/CHANGELOG.md | 7 + rum_salesforce_lwc/README.md | 638 ++++++++++++++++++ rum_salesforce_lwc/assets/service_checks.json | 1 + rum_salesforce_lwc/manifest.json | 34 + 4 files changed, 680 insertions(+) create mode 100644 rum_salesforce_lwc/CHANGELOG.md create mode 100644 rum_salesforce_lwc/README.md create mode 100644 rum_salesforce_lwc/assets/service_checks.json create mode 100644 rum_salesforce_lwc/manifest.json diff --git a/rum_salesforce_lwc/CHANGELOG.md b/rum_salesforce_lwc/CHANGELOG.md new file mode 100644 index 0000000000..26d6766e7e --- /dev/null +++ b/rum_salesforce_lwc/CHANGELOG.md @@ -0,0 +1,7 @@ +# CHANGELOG - Salesforce + +## 1.0.0 + +**_Added_**: + +* Initial Salesforce RUM Integration Tile. diff --git a/rum_salesforce_lwc/README.md b/rum_salesforce_lwc/README.md new file mode 100644 index 0000000000..99a59d5d34 --- /dev/null +++ b/rum_salesforce_lwc/README.md @@ -0,0 +1,638 @@ +# Salesforce Integration + +## Overview + +Instrument Salesforce Lightning Apps and Experience Cloud sites with Datadog Real User Monitoring using the Datadog Browser SDK slim RUM bundle. + +This guide covers four different deployment paths: + +- **[Lightning Apps](#lightning-apps)**: Use a custom Lightning Web Component loaded from the Utility Bar. +- **[Experience Cloud Head Markup](#experience-cloud-head-markup)**: Add the Datadog RUM initialization script directly to Head Markup. +- **[Experience Cloud Theme/Layout LWC](#experience-cloud-themelayout-lwc)**: Add a custom Lightning Web Component to an Experience Builder page, shared region, or theme/layout area. +- **[Feature Support](#salesforce-feature-support-matrix)**: Review supported features for the Datadog integration. + +**Note**: Use only one deployment path per Salesforce app or Experience Cloud site. + +## Setup + +You will need the following Datadog RUM values: + +- A Datadog RUM Application ID +- A Datadog RUM Client Token +- A Datadog site, such as `datadoghq.com` + +You can get those values in Datadog under **RUM > Digital Experience > Real User Monitoring > Manage Applications > Set Up Manually**. + +You should also enable [Lightning Web Security][1] in the Salesforce org. + +Finally, you need the [Datadog Slim RUM Bundle][2]. Download it into your Salesforce project's static resources folder, for example: + +```shell +curl -o staticresources/datadog_rum_slim.js https://www.datadoghq-browser-agent.com/us1/v7/datadog-rum-slim.js +``` + +## Lightning Apps + +Use this path for Salesforce LWC applications. + +This path uses: + +- A Salesforce Static Resource for the Datadog slim RUM bundle. +- A CSP Trusted Site for the Datadog browser intake endpoint. +- A custom Lightning Web Component. +- A Utility Bar configuration with eager loading enabled. + +### 1. Add the static resource + +Copy the Datadog slim RUM bundle into your Salesforce project and register it as a static resource. + +Suggested configuration: + +- Static Resource Name: `datadog_rum_slim` +- File location: `staticresources/datadog_rum_slim.js` +- Metadata location: `staticresources/datadog_rum_slim.resource-meta.xml` + +XML configuration: + +```xml + + + Public + application/javascript + +``` + +If you configure this through the Salesforce UI: + +1. Go to **Setup > Static Resources**. +2. Click **New**. +3. Set **Name** to `datadog_rum_slim`. +4. Upload the slim RUM JavaScript bundle. +5. Set **Cache Control** to `Public`. +6. Save the static resource. + +### 2. Add the CSP Trusted Site + +Allow Salesforce's Content Security Policy to connect to the Datadog browser intake endpoint. Without this configuration, the browser may block RUM events from being sent to Datadog. + +Suggested configuration: + +- File location: `cspTrustedSites/browser_intake_datadoghq_com.cspTrustedSite-meta.xml` + +XML configuration: + +```xml + + + All + Datadog browser RUM intake for US1 + https://browser-intake-datadoghq.com + true + true + +``` + +For non-US1 Datadog sites, update `endpointUrl` to match the correct Datadog browser intake endpoint for your region. + +### 3. Create the Datadog init component + +Create a Lightning Web Component that loads the Datadog Browser SDK and manually starts views as users navigate within the Lightning application. + +A Lightning Web Component bundle requires an HTML template. Create the following file first. + +File location: `lwc/datadogInit/datadogInit.html` + +```html + +``` + +### 4. Add the component JavaScript + +File location: `lwc/datadogInit/datadogInit.js` + +```javascript +import { LightningElement, api, wire } from 'lwc' +import { NavigationMixin, CurrentPageReference } from 'lightning/navigation' +import datadogRumSlim from '@salesforce/resourceUrl/datadog_rum_slim' +import { loadScript } from 'lightning/platformResourceLoader' + +let datadogInitialization +let lastStartedUrl + +export default class DatadogInit extends NavigationMixin(LightningElement) { + @api applicationId + @api clientToken + @api site + @api service + @api env + @api allowedTracingUrls + @api trackViewsManually + + connectedCallback() { + this.initialize() + } + + @wire(CurrentPageReference) + handleCurrentPageReference(pageReference) { + if (!pageReference) { + return + } + + this.initialize() + + if (window.DD_RUM) { + this.startViewForPageReference(pageReference) + } + } + + startViewForPageReference(pageReference) { + const urlPromise = this[NavigationMixin.GenerateUrl](pageReference) + urlPromise.then((url) => { + if (url === lastStartedUrl) { + return + } + lastStartedUrl = url + const absoluteUrl = new URL(url, window.location.origin).href + window.DD_RUM.startView({ name: url, url: absoluteUrl }) + }) + } + + initialize() { + if (!datadogInitialization) { + datadogInitialization = this.loadDatadogRum() + } + } + + loadDatadogRum() { + return loadScript(this, datadogRumSlim).then(() => { + const initConfig = { + applicationId: this.applicationId, + clientToken: this.clientToken, + env: this.env, + service: this.service, + site: this.site, + trackViewsManually: true, + trackEarlyRequests: true, + trackLongTasks: true, + trackResources: true, + trackUserInteractions: true, + } + window.DD_RUM.init(initConfig) + lastStartedUrl = window.location.pathname + window.location.search + window.location.hash + window.DD_RUM.startView({ + name: lastStartedUrl, + url: window.location.href, + }) + }) + } +} +``` + +### 5. Add the component metadata + +File location: `lwc/datadogInit/datadogInit.js-meta.xml` + +```xml + + + 64.0 + true + Datadog Init + + lightning__UtilityBar + + + + + + + + + + + +``` + +### 6. Add the component to a Lightning app + +Register the `datadogInit` component in your app's Utility Bar. You can do this through the Salesforce UI or by updating the app's FlexiPage metadata. + +**Important**: set the `eager` property to `true`. Without this setting, the SDK initializes only when the user manually opens the Utility Bar item, which can cause lost initial page-load data. + +File location: `flexipages/MyApp_UtilityBar.flexipage-meta.xml` + +```xml + + + eager + decorator + true + + datadogInit + datadogInit + +``` + +### 7. Validate the Lightning app installation + +After deploying the component: + +1. Open the Lightning app. +2. Open browser developer tools. +3. Confirm that the Datadog static resource loads successfully. +4. Confirm there are no CSP errors for the Datadog browser intake endpoint. +5. Navigate between Lightning pages. +6. In Datadog RUM Explorer, filter by the configured service and env. +7. Confirm that view events are created when navigation occurs. + +## Experience Cloud Head Markup + +Use this path for Experience Cloud sites where you can add custom JavaScript through Head Markup. This is usually the simplest Experience Cloud approach because the SDK loads at the page level and does not rely on the Salesforce Utility Bar. + +This path uses: + +- A Salesforce Static Resource for the Datadog slim RUM bundle. +- Experience Cloud CSP configuration. +- A Head Markup script that loads the SDK and tracks route changes. + +### 1. Add the static resource + +Copy the Datadog slim RUM bundle into your Salesforce project and register it as a static resource. + +Suggested configuration: + +- Static Resource Name: `datadog_rum_slim` +- File location: `staticresources/datadog_rum_slim.js` +- Metadata location: `staticresources/datadog_rum_slim.resource-meta.xml` + +XML configuration: + +```xml + + + Public + application/javascript + +``` + +If you configure this through the Salesforce UI: + +1. Go to **Setup > Static Resources**. +2. Click **New**. +3. Set **Name** to `datadog_rum_slim`. +4. Upload the slim RUM JavaScript bundle. +5. Set **Cache Control** to `Public`. +6. Save the static resource. + +### 2. Open the Experience Cloud site in Builder + +1. Go to **Setup > Apps > App Manager**. +2. Search for your Experience Cloud application. +3. Click **Manage**. +4. When the page loads, click **Builder**. + +### 3. Configure CSP for the Datadog intake endpoint + +In Experience Builder: + +1. Go to **Settings > Security & Privacy**. +2. Change the security level from **Strict CSP** to **Relaxed CSP**. +3. Add the Datadog browser intake endpoint as a trusted site. + +Use the following trusted site configuration for US1: + +| Field | Value | +| ----- | ----------------------------------- | +| Name | `browser_intake_datadoghq_com` | +| URL | `https://browser-intake-datadoghq.com` | + +For non-US1 Datadog sites, use the intake endpoint for the correct Datadog site. + +### 4. Add the Head Markup script + +In Experience Builder: + +1. Go to **Settings > Advanced**. +2. Open **Head Markup**. +3. Click **Edit Head Markup**. +4. Paste the following script. +5. Replace the placeholder values with your Datadog RUM configuration. + +```html + + +``` + +### 5. Publish the Experience Cloud site + +After adding the Head Markup script: + +1. Save the Head Markup configuration. +2. Publish the Experience Cloud site. +3. Open the published site in a new browser session. +4. Confirm that the Datadog static resource loads. +5. Confirm that no CSP errors appear in the browser console. +6. Navigate between site pages. +7. Confirm that RUM view events appear in Datadog. + +## Experience Cloud Theme/Layout LWC + +Use this path when you want to instrument an Experience Cloud site with a Lightning Web Component instead of Head Markup. + +This path is useful when: + +- Head Markup is unavailable. +- You want RUM configuration to be managed through Experience Builder component properties. +- You want to place the initializer in a shared region, template, page layout, or theme/layout area. +- You want to reuse the LWC-based implementation pattern across Salesforce surfaces. + +Unlike Lightning Apps, Experience Cloud does not use the Utility Bar. The `datadogInit` component must be placed somewhere that loads on every page where RUM should run: + +- For simple installations, expose the component as an Experience Builder page component and place it in a shared region that appears across the site. +- For custom LWR theme layouts, include the initializer inside your existing custom theme layout wrapper. + +This path uses: + +- A Salesforce Static Resource for the Datadog slim RUM bundle. +- Experience Cloud CSP configuration. +- A custom Lightning Web Component exposed to Experience Builder. +- Placement in a shared site region, page template, or theme/layout area. + +### 1. Add the static resource + +Copy the Datadog slim RUM bundle into your Salesforce project and register it as a static resource. + +Suggested configuration: + +- Static Resource Name: `datadog_rum_slim` +- File location: `staticresources/datadog_rum_slim.js` +- Metadata location: `staticresources/datadog_rum_slim.resource-meta.xml` + +XML configuration: + +```xml + + + Public + application/javascript + +``` + +If you configure this through the Salesforce UI: + +1. Go to **Setup > Static Resources**. +2. Click **New**. +3. Set **Name** to `datadog_rum_slim`. +4. Upload the slim RUM JavaScript bundle. +5. Set **Cache Control** to `Public`. +6. Save the static resource. + +### 2. Configure CSP for the Datadog intake endpoint + +In Experience Builder: + +1. Go to **Settings > Security & Privacy**. +2. Change the security level from **Strict CSP** to **Relaxed CSP**. +3. Add the Datadog browser intake endpoint as a trusted site. + +Use the following trusted site configuration for US1: + +| Field | Value | +| ----- | ----------------------------------- | +| Name | `browser_intake_datadoghq_com` | +| URL | `https://browser-intake-datadoghq.com` | + +For non-US1 Datadog sites, use the intake endpoint for the correct Datadog site. + +### 3. Create the Datadog init component + +Create an LWC that loads the Datadog Browser SDK and manually starts views as users navigate within the Experience Cloud site. + +A Lightning Web Component bundle requires an HTML template. + +File location: `lwc/datadogInit/datadogInit.html` + +```html + +``` + +### 4. Add the component JavaScript + +File location: `lwc/datadogInit/datadogInit.js` + +```javascript +import { LightningElement, api, wire } from 'lwc' +import { NavigationMixin, CurrentPageReference } from 'lightning/navigation' +import datadogRumSlim from '@salesforce/resourceUrl/datadog_rum_slim' +import { loadScript } from 'lightning/platformResourceLoader' + +let datadogInitialization +let lastStartedUrl + +export default class DatadogInit extends NavigationMixin(LightningElement) { + @api applicationId + @api clientToken + @api site + @api service + @api env + @api allowedTracingUrls + @api trackViewsManually + + connectedCallback() { + this.initialize() + } + + @wire(CurrentPageReference) + handleCurrentPageReference(pageReference) { + if (!pageReference) { + return + } + + this.initialize() + + if (window.DD_RUM) { + this.startViewForPageReference(pageReference) + } + } + + startViewForPageReference(pageReference) { + const urlPromise = this[NavigationMixin.GenerateUrl](pageReference) + urlPromise.then((url) => { + if (url === lastStartedUrl) { + return + } + lastStartedUrl = url + const absoluteUrl = new URL(url, window.location.origin).href + window.DD_RUM.startView({ name: url, url: absoluteUrl }) + }) + } + + initialize() { + if (!datadogInitialization) { + datadogInitialization = this.loadDatadogRum() + } + } + + loadDatadogRum() { + return loadScript(this, datadogRumSlim).then(() => { + const initConfig = { + applicationId: this.applicationId, + clientToken: this.clientToken, + env: this.env, + service: this.service, + site: this.site, + trackViewsManually: true, + trackEarlyRequests: true, + trackLongTasks: true, + trackResources: true, + trackUserInteractions: true, + } + window.DD_RUM.init(initConfig) + lastStartedUrl = window.location.pathname + window.location.search + window.location.hash + window.DD_RUM.startView({ + name: lastStartedUrl, + url: window.location.href, + }) + }) + } +} +``` + +### 5. Add the component metadata for Experience Builder + +Expose the component to Experience Builder: + +- Use `lightningCommunity__Page` so the component can be placed through Experience Builder. +- Use `lightningCommunity__Default` so the Datadog configuration values can be edited as component properties. + +File location: `lwc/datadogInit/datadogInit.js-meta.xml` + +```xml + + + 64.0 + true + Datadog Init + + lightningCommunity__Page + lightningCommunity__Default + + + + + + + + + + + +``` + +If you are using the same `datadogInit` component for both Lightning Apps and Experience Cloud, combine the targets into one metadata file: + +```xml + + lightning__UtilityBar + lightningCommunity__Page + lightningCommunity__Default + +``` + +Then configure both target groups in `targetConfigs` as needed. + +### 6. Add the component to an Experience Builder theme/layout area + +Open the Experience Cloud site in Builder: + +1. Go to **Setup > Apps > App Manager**. +2. Search for your Experience Cloud application. +3. Click **Manage**. +4. Click **Builder**. + +Add the Datadog Init component to a location that loads on every page where RUM should run. Recommended placements include: + +- A shared site region. +- A shared page template. +- A global header or footer region. +- A theme/layout area that is rendered across the site. + +After adding the component: + +1. Select the Datadog Init component. +2. Set the component properties: `applicationId`, `clientToken`, `site`, `service`, `env`. +3. Save the site. +4. Publish the site. + +### 7. Validate the Theme/Layout LWC installation + +After publishing the site: + +1. Open the Experience Cloud site in a new browser session. +2. Open browser developer tools. +3. Confirm that the Datadog static resource loads successfully. +4. Confirm there are no CSP errors for the Datadog browser intake endpoint. +5. Navigate between site pages. +6. Confirm that RUM view events appear in Datadog. + +If the component is accidentally added multiple times, the global initialization guard prevents duplicate SDK initialization, but the component should still be placed only once for clarity and maintainability. + +## Salesforce Feature Support Matrix + +The following table outlines SDK feature support within the Lightning Web Security (LWS) sandbox environment. + +| Feature Area | Supported | Notes | +| ---------------------------- | ------------ | -------------------------------------------- | +| **View Events** | | | +| Initial View | Yes | Automatic on init. | +| Manual Tracking | Yes | Supported via `startView`. | +| Navigation Timings | Yes | Collected via performance API. | +| Web Vitals | Yes | | +| **Resource Events** | | | +| Fetch / XHR | Limited (2) | Context payload inaccessible. | +| Other Resources | Yes | CSS, images, etc. | +| APM Correlation | Limited (2) | Requires header injection. | +| **Action Events** | | | +| Custom Actions | Yes | Supported via `addAction`. (5) Not supported on the Head Markup path. | +| Click Actions | Yes | (3) Shadow DOM boundaries apply. | +| Frustration Signals | Yes | | +| Loading Time | Limited (1) | Network detection may be incomplete. | +| **Error Events** | | | +| Console / Custom | Yes | Captured via instrumentation. (5) Not supported on the Head Markup path. | +| Runtime Errors | Limited (4) | Often redacted as "Script error." | +| Unhandled Rejection | No | Event not supported in LWS. | +| **Other** | | | +| Vital Events | Yes | | +| Long Task Events | Yes | | +| Session Replay | No | DOM/Worker constraints prevent support. | + +Footnotes: + +1. **Loading Time**: Ends when no pending network requests are detected. LWS may hide some fetch/XHR activity. +2. **Limited Context**: Inaccessible sandbox objects mean `beforeSend` cannot access response bodies or full XHR objects. +3. **Selectors**: Due to shadow boundaries, `event.target` may reflect the component host rather than the inner element. +4. **Runtime Errors**: Errors passing through the Lightning shell may lose stack traces and original error objects. +5. **Head Markup limitation**: The Experience Cloud Head Markup path has no component context to call `addAction` or `addError`, so custom actions and custom error tracking are not supported there. + +## Troubleshooting + +Need help? Contact [Datadog Support][3]. + +[1]: https://help.salesforce.com/s/articleView?id=sf.lwc_lwsec_enable.htm +[2]: https://www.datadoghq-browser-agent.com/us1/v7/datadog-rum-slim.js +[3]: https://docs.datadoghq.com/help/ diff --git a/rum_salesforce_lwc/assets/service_checks.json b/rum_salesforce_lwc/assets/service_checks.json new file mode 100644 index 0000000000..fe51488c70 --- /dev/null +++ b/rum_salesforce_lwc/assets/service_checks.json @@ -0,0 +1 @@ +[] diff --git a/rum_salesforce_lwc/manifest.json b/rum_salesforce_lwc/manifest.json new file mode 100644 index 0000000000..b22cf29884 --- /dev/null +++ b/rum_salesforce_lwc/manifest.json @@ -0,0 +1,34 @@ +{ + "manifest_version": "2.0.0", + "app_uuid": "2e290a82-8d2c-4ecd-a139-8dfeb8ed0474", + "app_id": "rum-salesforce-lwc", + "owner": "rum-browser", + "display_on_public_website": true, + "tile": { + "overview": "README.md#Overview", + "configuration": "README.md#Setup", + "support": "README.md#Troubleshooting", + "changelog": "CHANGELOG.md", + "description": "Monitor Salesforce Lightning Apps and Experience Cloud sites using Datadog RUM", + "title": "Salesforce", + "media": [], + "classifier_tags": [ + "Category::Metrics", + "Category::Network", + "Category::Tracing", + "Supported OS::Android", + "Supported OS::Linux", + "Supported OS::Windows", + "Supported OS::iOS", + "Supported OS::macOS", + "Offering::Integration" + ] + }, + "author": { + "support_email": "help@datadoghq.com", + "name": "Datadog", + "homepage": "https://www.datadoghq.com", + "sales_email": "info@datadoghq.com" + }, + "assets": {} +} From dcb70cf1ae4af0c7814f733a742a0ce18ea24aa7 Mon Sep 17 00:00:00 2001 From: "beltran.bulbarella" Date: Fri, 10 Jul 2026 12:12:54 +0200 Subject: [PATCH 2/3] Add codeowners and remove service checks --- .github/CODEOWNERS | 1 + rum_salesforce_lwc/assets/service_checks.json | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) delete mode 100644 rum_salesforce_lwc/assets/service_checks.json diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index a243f1f45c..3b4f2dbe63 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -191,6 +191,7 @@ code-coverage.datadog.yml @DataDog/agent-integr /rum_react/ @DataDog/rum-app @DataDog/rum-browser /rum_react_native/ @DataDog/rum-app @DataDog/rum-mobile /rum_roku/ @DataDog/rum-app @DataDog/rum-mobile +/rum_salesforce_lwc/ @DataDog/rum-app @DataDog/rum-browser /rum_vue/ @DataDog/rum-app @DataDog/rum-browser /rundeck/ forrest@rundeck.com /scalr/ @soltysss @DataDog/ecosystems-review diff --git a/rum_salesforce_lwc/assets/service_checks.json b/rum_salesforce_lwc/assets/service_checks.json deleted file mode 100644 index fe51488c70..0000000000 --- a/rum_salesforce_lwc/assets/service_checks.json +++ /dev/null @@ -1 +0,0 @@ -[] From c512aa7ba8f078f734c8de1661d09f5f208c038a Mon Sep 17 00:00:00 2001 From: "beltran.bulbarella" Date: Fri, 10 Jul 2026 19:42:06 +0200 Subject: [PATCH 3/3] Address comments from review --- rum_salesforce_lwc/README.md | 17 +++++++++-------- rum_salesforce_lwc/manifest.json | 2 +- 2 files changed, 10 insertions(+), 9 deletions(-) diff --git a/rum_salesforce_lwc/README.md b/rum_salesforce_lwc/README.md index 99a59d5d34..cf00b6d1e1 100644 --- a/rum_salesforce_lwc/README.md +++ b/rum_salesforce_lwc/README.md @@ -4,7 +4,7 @@ Instrument Salesforce Lightning Apps and Experience Cloud sites with Datadog Real User Monitoring using the Datadog Browser SDK slim RUM bundle. -This guide covers four different deployment paths: +This guide covers three deployment paths, plus a feature support reference: - **[Lightning Apps](#lightning-apps)**: Use a custom Lightning Web Component loaded from the Utility Bar. - **[Experience Cloud Head Markup](#experience-cloud-head-markup)**: Add the Datadog RUM initialization script directly to Head Markup. @@ -21,7 +21,7 @@ You will need the following Datadog RUM values: - A Datadog RUM Client Token - A Datadog site, such as `datadoghq.com` -You can get those values in Datadog under **RUM > Digital Experience > Real User Monitoring > Manage Applications > Set Up Manually**. +You can get those values in Datadog under **Digital Experience > Real User Monitoring > Manage Applications > Set Up Manually**. You should also enable [Lightning Web Security][1] in the Salesforce org. @@ -247,7 +247,7 @@ After deploying the component: ## Experience Cloud Head Markup -Use this path for Experience Cloud sites where you can add custom JavaScript through Head Markup. This is usually the simplest Experience Cloud approach because the SDK loads at the page level and does not rely on the Salesforce Utility Bar. +Use this path for Experience Cloud sites where you can add custom JavaScript through Head Markup. This is usually the most direct Experience Cloud approach because the SDK loads at the page level and does not rely on the Salesforce Utility Bar. This path uses: @@ -306,7 +306,7 @@ Use the following trusted site configuration for US1: | Name | `browser_intake_datadoghq_com` | | URL | `https://browser-intake-datadoghq.com` | -For non-US1 Datadog sites, use the intake endpoint for the correct Datadog site. +For non-US1 Datadog sites, use the intake endpoint for the correct [Datadog site][4]. ### 4. Add the Head Markup script @@ -363,7 +363,7 @@ This path is useful when: Unlike Lightning Apps, Experience Cloud does not use the Utility Bar. The `datadogInit` component must be placed somewhere that loads on every page where RUM should run: -- For simple installations, expose the component as an Experience Builder page component and place it in a shared region that appears across the site. +- For lightweight installations, expose the component as an Experience Builder page component and place it in a shared region that appears across the site. - For custom LWR theme layouts, include the initializer inside your existing custom theme layout wrapper. This path uses: @@ -417,7 +417,7 @@ Use the following trusted site configuration for US1: | Name | `browser_intake_datadoghq_com` | | URL | `https://browser-intake-datadoghq.com` | -For non-US1 Datadog sites, use the intake endpoint for the correct Datadog site. +For non-US1 Datadog sites, use the intake endpoint for the correct [Datadog site][4]. ### 3. Create the Datadog init component @@ -600,7 +600,7 @@ The following table outlines SDK feature support within the Lightning Web Securi | ---------------------------- | ------------ | -------------------------------------------- | | **View Events** | | | | Initial View | Yes | Automatic on init. | -| Manual Tracking | Yes | Supported via `startView`. | +| Manual Tracking | Yes | Supported through `startView`. | | Navigation Timings | Yes | Collected via performance API. | | Web Vitals | Yes | | | **Resource Events** | | | @@ -608,7 +608,7 @@ The following table outlines SDK feature support within the Lightning Web Securi | Other Resources | Yes | CSS, images, etc. | | APM Correlation | Limited (2) | Requires header injection. | | **Action Events** | | | -| Custom Actions | Yes | Supported via `addAction`. (5) Not supported on the Head Markup path. | +| Custom Actions | Yes | Supported through `addAction`. (5) Not supported on the Head Markup path. | | Click Actions | Yes | (3) Shadow DOM boundaries apply. | | Frustration Signals | Yes | | | Loading Time | Limited (1) | Network detection may be incomplete. | @@ -636,3 +636,4 @@ Need help? Contact [Datadog Support][3]. [1]: https://help.salesforce.com/s/articleView?id=sf.lwc_lwsec_enable.htm [2]: https://www.datadoghq-browser-agent.com/us1/v7/datadog-rum-slim.js [3]: https://docs.datadoghq.com/help/ +[4]: https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site diff --git a/rum_salesforce_lwc/manifest.json b/rum_salesforce_lwc/manifest.json index b22cf29884..44bb8fc86a 100644 --- a/rum_salesforce_lwc/manifest.json +++ b/rum_salesforce_lwc/manifest.json @@ -10,7 +10,7 @@ "support": "README.md#Troubleshooting", "changelog": "CHANGELOG.md", "description": "Monitor Salesforce Lightning Apps and Experience Cloud sites using Datadog RUM", - "title": "Salesforce", + "title": "Salesforce (RUM)", "media": [], "classifier_tags": [ "Category::Metrics",