
Datadog Extends RUM to Shopify and Salesforce — Monitoring Revenue Flows You Don't Control
Enterprise Developer PlatformsMost observability tooling assumes you control the frontend code. Real User Monitoring works by embedding an SDK — you add the JavaScript to your pages, instrument the events that matter, and Datadog captures the session data. This works well for products you build and deploy.
It doesn’t work for Shopify checkouts, Salesforce Experience Cloud portals, or any frontend that lives on a platform you configure rather than code. These are exactly the environments where critical business events happen — a checkout abandonment, a portal error, a payment failure — and exactly where standard RUM instrumentation has been unavailable.
The new Shopify and Salesforce integrations close that gap.
Shopify Integration
What it captures:
- Continuous session tracking from storefront through checkout completion
- Checkout funnel visualization and conversion analysis
- Pageviews, clicks, and UI extension errors (automatic)
- Checkout-specific events with manual instrumentation: validation errors, payment declines, shipping method selection
- User segmentation by conversion status, device, geography, referrer
- Feature flag correlation with checkout completion rates
The architectural constraint: Shopify’s checkout pages run in a controlled environment that restricts which JavaScript executes. Datadog’s approach uses a Liquid snippet on the storefront (where the full SDK can run) and a custom Datadog pixel in Shopify Admin for checkout pages. This covers the conversion path; it doesn’t give you Session Replay or Core Web Vitals inside the checkout iframe specifically, only on the storefront pages where the full SDK runs.
For engineering teams: you can see that users are dropping at a specific checkout step, and you can correlate that with error events. You can’t replay the exact session frame-by-frame inside the checkout itself.
Implementation: Add the Liquid snippet to storefront theme templates, then configure the Datadog custom pixel in Shopify Admin under Settings → Customer Events.
Salesforce Experience Cloud Integration
What it captures:
- View tracking using Salesforce’s navigation events (distinct views even when URLs are identical — a common problem in Lightning component architectures where URL-based page detection fails)
- Console errors and custom errors within Lightning Web Security boundaries
- Click tracking and custom action events with frustration signals (rage clicks, dead clicks)
- Core Web Vitals correlated with user interactions
The architectural constraint: Salesforce’s Lightning Web Security sandbox limits what runtime information is accessible from within components. Unhandled promise rejections aren’t captured because the sandbox intercepts them before they surface to Datadog’s error collection. Error messages from within the sandbox may lack stack trace detail that would be available in a standard browser context.
For engineering teams: you get visibility into error rates, user behavior patterns, and performance bottlenecks in your Salesforce portal. You don’t get the same error forensics detail you’d have on an application you built and deployed directly.
Implementation: Upload the Datadog bundle as a Static Resource in Salesforce, then load it via loadScript from your Lightning Web Components.
Why These Integrations Exist Now
Platform-hosted frontends have proliferated as companies adopt commercial SaaS for customer-facing workflows rather than building them. Your checkout flow may live on Shopify; your customer portal on Salesforce or ServiceNow; your support interface on Zendesk. These platforms handle significant user interaction while being outside your direct code control.
For engineering teams responsible for revenue metrics and reliability SLAs on these flows: observability without SDK access has historically meant relying on platform-native analytics (Shopify Analytics, Salesforce reports) that don’t integrate with your broader monitoring infrastructure.
The Datadog integrations bring Shopify and Salesforce session data into the same observability platform as your backend services, infrastructure metrics, and other frontend applications. When a checkout conversion drop correlates with a payment service latency spike, you can see both in the same context — rather than looking at Shopify Analytics in one tab and Datadog APM in another.
The So What
For engineering teams using Datadog for observability who also run customer-facing flows on Shopify or Salesforce: these integrations are worth instrumenting. The gap between “we monitor our services” and “we monitor the full customer journey” closes meaningfully when the checkout funnel and customer portal generate Datadog events alongside everything else.
The constraint to understand upfront: platform sandbox restrictions mean these integrations are not equivalent to standard RUM. You get funnel visibility and error detection, not full session replay inside the restricted environments. For most teams evaluating conversion optimization or investigating checkout errors, funnel visibility and error rates are the data that matters — but set expectations appropriately if you’re replacing a session recording tool rather than adding funnel analytics to existing observability.
Source: Datadog
Content created with AI assistance and reviewed for accuracy.
Join the conversation
Stack Insiders is our free community for readers who want to go deeper — share resources, ask questions, and connect with others across every vertical we cover.
Join Stack Insiders →