✅ Add Salesforce Experience Cloud Head Markup E2E

[BeltranBulbarellaDD]

Motivation

Validate the Salesforce RUM bundle when it is initialized from Experience Cloud Head Markup instead of from a Lightning Web Component.

This covers the recommended initialization path for an Experience Cloud site while continuing to exercise views, resources, long tasks, automatic actions, and runtime errors.

Changes

• Add experience-cloud-headmarkup as a supported Salesforce test application.
• Generate sf-experience-headmarkup-app from sf-experience-app.
  • Remove the experienceDatadogInit LWC because RUM is initialized by the site's Head Markup.
  • Keep the generated application out of source control and formatting/linting.
• Update the Salesforce deployment script to:
  • Support the Head Markup site.
  • Build selected Salesforce applications before deployment.
  • Refresh their Salesforce RUM static resources through the standard app build.
• Add the Head Markup site's public URL to the E2E framework.
• Inject RUM_CONFIGURATION and RUM_CONTEXT before the Salesforce page loads so the configured Head Markup can use the E2E intake configuration.
• Run the existing Salesforce RUM scenarios against the Head Markup site.
  • Custom actions, custom errors, and custom vitals are excluded because the Experience components cannot access the RUM instance initialized by Head Markup.
  • Automatic interactions, runtime errors, views, resources, and long tasks remain covered.
• Remove duplicated RUM setup instructions from the Experience Cloud test app README in favor of the canonical Salesforce integration documentation.

The Experience Cloud site itself must be configured separately in Experience Builder with the RUM initialization Head Markup, CSP permissions, guest access, and a published Product Explorer page.

Test instructions

1. Run: salesforce:get-urls.

2. Navigate to that URL, check that the SDK gets initiated and sends events.

3. Run the focused E2E tests:

   yarn test:e2e -g "salesforce experience-cloud-headmarkup"

Checklist

• Tested locally
• Tested on staging
• Added unit tests for this change — not applicable
• Added e2e/integration tests for this change
• Updated relevant documentation

[datadog-datadog-us1-prod]

 

⚠️ Warnings

🚦 1 Pipeline job failed

Lint PR title | lint     

See error

PR title must start with one of the allowed gitmoji prefixes. Current title: 'Beltran.bulbarella/add sf headmarkup app'.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 77.15% (-0.06%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: c2b1b4a | Docs | Datadog PR Page | Give us feedback!}

[cit-pr-commenter-54b7da]

Bundles Sizes Evolution

📦 Bundle Name	Base Size	Local Size	𝚫	𝚫%	Status
Rum	180.59 KiB	180.59 KiB	0 B	0.00%	✅
Rum Profiler	8.43 KiB	8.43 KiB	0 B	0.00%	✅
Rum Recorder	21.12 KiB	21.12 KiB	0 B	0.00%	✅
Logs	57.05 KiB	57.05 KiB	0 B	0.00%	✅
Rum Salesforce	N/A	138.47 KiB	N/A	N/A	N/A
Rum Slim	138.46 KiB	138.46 KiB	0 B	0.00%	✅
Worker	22.96 KiB	22.96 KiB	0 B	0.00%	✅
Rum Shopify	N/A	200.17 KiB	N/A	N/A	N/A
Rum-shopify Profiler	N/A	8.43 KiB	N/A	N/A	N/A
Rum-shopify Recorder	N/A	3.72 KiB	N/A	N/A	N/A

[BeltranBulbarellaDD]

@codex pls review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: c2b1b4abc8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".