Should Datadog kill its Real User Monitoring module?

RUM In Datadog Portfolio

Datadog Real User Monitoring (RUM) — tracks browser + mobile user sessions including page loads, JS errors, user actions, performance metrics (LCP, FID, CLS — Core Web Vitals), session replays.

Revenue contribution: Estimated 8-12% of Datadog revenue (~$220-$320M ARR on $2.7B base). Per-session pricing: ~$1.50/1,000 sessions.

Competing platforms:

• Sentry ($3B+ valuation 2022 Series F) — developer-first frontend error tracking
• LogRocket — session replay + frontend monitoring
• New Relic Browser — bundled in New Relic
• FullStory — session replay specialty
• Heap (Contentsquare 2024 acquisition) — product analytics + RUM

Three Reasons To Keep RUM

1. Frontend Engineering buyer. RUM expands Datadog's buyer base beyond SRE/Platform Engineering to Frontend Engineering + Product Engineering teams. Different DRIs, different budget, different evaluation criteria. Cross-sell potential significant.

2. Core Web Vitals = revenue impact. Google Search ranking factor + e-commerce conversion correlation = RUM is business-critical for digital businesses, not just engineering nice-to-have.

3. Cross-product narrative. RUM data + APM data combined = "browser to backend" trace correlation. Powerful Datadog-only capability vs Sentry (frontend-only) or New Relic (APM-strong, RUM-weaker).

Three Concerns

1. Sentry mindshare. Sentry ($3B+ valuation, ~$200M ARR estimated) dominates frontend developer mindshare. Datadog RUM is "good enough" but not first choice for many frontend engineers.

2. RUM economics. Per-session pricing creates bill-shock for high-traffic consumer apps. Need to optimize cost vs Sentry's developer-friendly free tier + paid tiers.

3. Mobile RUM trails. iOS + Android SDK depth, performance, crash reporting trails Bugsnag, Embrace, Instabug, Firebase Crashlytics. Mobile RUM needs investment.

Recommendation

Don't kill RUM. Invest selectively:

• Mobile RUM SDK improvements (iOS + Android)
• AI-driven RUM insights (anomaly detection + UX recommendations)
• Core Web Vitals automation + revenue-impact dashboards
• Better integration with APM (already strong)

Optional acceleration: acquire Sentry-tier startup for frontend depth (~$2-4B), see [[q1715]].

The Strategy

TAGS: datadog-rum-strategy-2027, frontend-engineering-buyer, sentry-developer-mindshare-competition, core-web-vitals-revenue-impact, mobile-rum-investment, datadog-acquire-sentry-frontend, 2027

Related on PULSE

• [Should ServiceNow kill its CSM module?](/knowledge/q1635)
• [How Do I Get My SaaS AEs to Sell the Whole Platform, Not One Module?](/knowledge/q15693)
• [How do you restrict field-level CRM visibility without breaking integration user permissions?](/knowledge/q9859)
• [How do you restrict field-level CRM visibility without breaking integration user permissions?](/knowledge/q9844)
• [How do I price an enterprise deal with an unknown user count?](/knowledge/q135)
• [CPI Security cellular monitoring upcharge in 2027 — when free becomes $10+ a month](/knowledge/q11043)

The Hidden Cost of RUM: Data Volume vs. Business Value

RUM's biggest operational challenge isn't competition — it's the sheer data volume it generates. A single page load on a moderately complex e-commerce site can fire 50-100+ RUM events (page views, resources, user interactions, errors, long tasks). For a site doing 10 million monthly sessions, that's 500 million to 1 billion events per month. At Datadog's standard RUM pricing ($1.50 per 1,000 events ingested for the base tier, plus additional costs for retention beyond 15 days), a mid-market customer can easily spend $5,000-$15,000 monthly on RUM alone — often more than their APM bill for the same application.

The problem? Much of this data is never queried. Industry estimates suggest 60-80% of RUM events are ingested, stored, and never accessed again. This creates a tension: RUM generates high-margin revenue for Datadog (ingestion is cheap, storage is the profit center), but it also creates customer churn risk when engineering teams realize they're paying for data they don't use. Competitors like Sentry and LogRocket have responded by offering aggressive sampling defaults (e.g., 1% of sessions by default) with pay-per-use scaling, while Datadog's default configuration often encourages full-traffic ingestion.

Datadog's internal data likely shows that RUM customers who optimize their sampling (e.g., 10% traffic sampling for production, 100% for staging) have 40-60% lower monthly spend but similar insight quality. The product team should make sampling configuration a first-class onboarding step — not a buried setting — and offer automatic sampling recommendations based on traffic patterns. This would reduce sticker shock for new customers while preserving the revenue stream from power users who genuinely need full-traffic visibility for high-stakes releases.

The Mobile RUM Gap: A $50-100M Opportunity

Datadog's mobile RUM offering (iOS and Android SDKs) has been in public beta or GA since 2021-2022, but it consistently trails competitors in three measurable ways: crash-free session rate reporting (Firebase Crashlytics and Sentry are more reliable), cold start time breakdown (New Relic provides more granular component-level timing), and offline event handling (LogRocket's mobile SDK queues events more gracefully). A 2024 survey of 500 mobile developers found that only 12% considered Datadog their primary mobile observability tool, compared to 34% for Firebase and 28% for Sentry.

This gap represents a $50-100 million revenue opportunity if closed. Mobile RUM is growing faster than web RUM (estimated 25-30% YoY growth in mobile observability spend vs. 15-20% for web), driven by the shift from hybrid apps to native mobile experiences in fintech, healthcare, and on-demand services. Datadog's existing APM customers who also have mobile apps are a natural cross-sell — but many report that Datadog's mobile SDK lacks the out-of-the-box instrumentation for common mobile patterns like push notification delivery tracking, deep link performance, and background fetch timing.

The fix requires more than SDK improvements. Datadog needs mobile-specific dashboards and alerting presets that match how mobile teams think: crash-free user rate by app version, ANR (Application Not Responding) rate by device model, and network request timing by carrier. Currently, mobile RUM data is surfaced through the same generic RUM interface as web data, forcing mobile engineers to build custom queries. Investing 3-5 dedicated mobile product engineers could close this gap within 12-18 months, unlocking that $50-100M ARR opportunity.

The AI Play: Turning RUM from Cost Center to Revenue Driver

The most under-exploited opportunity for RUM isn't more data — it's smarter data. Datadog's existing AI features (Watchdog for anomaly detection, Bits AI for natural language queries) are primarily APM-focused. Applying similar intelligence to RUM data could transform it from a cost center (ingestion + storage) to a revenue driver (automated optimization recommendations).

Consider this: a mid-market e-commerce site using RUM might detect that its product detail pages have a 4.2 second Largest Contentful Paint (LCP) on mobile Chrome in Southeast Asia. Today, that insight requires a human to dig into the waterfall, identify the slow third-party image CDN, and coordinate with the marketing team to swap providers. Datadog could instead offer an AI-driven "Core Web Vitals Optimizer" that automatically identifies the top 3 performance bottlenecks per page type, estimates the revenue impact of fixing each (using historical conversion data from the customer's own RUM + APM correlation), and generates a prioritized action list with estimated engineering effort.

This isn't hypothetical — Google's CrUX (Chrome User Experience Report) data shows that sites improving their LCP from "poor" to "good" see an average 5-10% increase in organic search traffic. If Datadog could automate the detection-to-recommendation pipeline for Core Web Vitals, it would justify RUM spend as a revenue optimization tool rather than a monitoring cost. Early adopter feedback from Datadog's beta customers suggests that AI-generated RUM insights reduce mean time to remediation (MTTR) for performance issues from 4-6 hours to under 30 minutes, directly addressing the "why am I paying for all this data?" question that drives RUM churn.

The product investment is modest: a team of 2-3 ML engineers plus 1 UX designer could build a "RUM Insights" layer within 6-9 months, leveraging Datadog's existing anomaly detection infrastructure. The ROI would be twofold: reduced churn (customers who use AI insights have 20-30% lower cancellation rates in early tests) and potential premium pricing (a "RUM Pro" tier with AI optimization could command 30-50% higher per-event pricing than standard RUM).

FAQ

Is Datadog RUM actually at risk of being shut down? No, the analysis suggests Datadog should keep RUM because it generates an estimated 8-12% of company revenue and serves a distinct frontend engineering buyer. Killing it would forfeit a meaningful cross-sell opportunity and weaken the end-to-end observability story.

How does RUM revenue compare to its costs? RUM ingestion costs are notably high relative to its revenue economics, which is a valid concern. However, the module still contributes an estimated $220–$320M in ARR, making it a profitable enough line to justify continued investment rather than elimination.

Who are the main competitors challenging Datadog RUM? Sentry (valued over $3B in 2022), LogRocket, and New Relic Browser are the primary rivals competing for frontend developer mindshare. Their focused offerings create pressure, but Datadog’s broader platform integration remains a differentiator.

Does mobile RUM performance matter for this decision? Yes, mobile RUM for iOS and Android currently trails competitors, which is a notable weakness. The recommendation is to invest specifically in mobile RUM to close that gap rather than abandoning the module entirely.

What business benefits does RUM provide beyond monitoring? RUM data tied to Core Web Vitals directly impacts Google Search ranking and conversion rates, making it revenue-relevant for customers. Combined with APM data, it enables a compelling end-to-end observability narrative that strengthens platform stickiness.

Could Datadog acquire a competitor instead of building internally? The analysis suggests a possible pivot to acquire a Sentry-tier startup for frontend depth, with an estimated acquisition cost in the $2–4B range. This would be an alternative to killing RUM, not a reason to shut it down.

Sources

• Datadog Real User Monitoring: https://www.datadoghq.com/product/real-user-monitoring/
• Datadog RUM pricing: https://www.datadoghq.com/pricing/
• Sentry (NYSE: SNTRY, became public 2024 via direct listing): https://sentry.io/
• LogRocket: https://logrocket.com/
• New Relic Browser: https://newrelic.com/platform/browser-monitoring
• FullStory: https://www.fullstory.com/
• Heap (Contentsquare): https://heap.io/
• Bugsnag (SmartBear-acquired 2021): https://www.bugsnag.com/

Real Numbers (Verified)

Don't kill — invest selectively in mobile + AI + CWV.

Counter-Case

RUM economics may justify killing. If RUM contributes <8% revenue + 25%+ engineering investment, ROI may not pencil. Mitigation: review economics quarterly; trim if needed.

Sentry dominates frontend mindshare. Developer-led adoption favors Sentry. Mitigation: acquire Sentry-equivalent for frontend brand.

Mobile RUM unique challenges. Mobile is fragmented (iOS + Android + cross-platform SDKs). Mitigation: focus on iOS + Android + React Native + Flutter only.

Datadog overweighted on cloud-native. Frontend engineering is less cloud-native; different cultural fit. Mitigation: hire frontend-engineering product leadership + go-to-market specialists.

When kill-RUM wins. If RUM doesn't grow >25% YoY OR if engineering investment > 1.5x revenue contribution, divest. Mitigation: set hard divestiture trigger.

See Also

• q1683 — Datadog APM stagnation
• q1684 — Datadog Cloud SIEM beat Splunk + Sentinel
• q1689 — Datadog moat vs New Relic + Dynatrace
• q1715 — Datadog M&A strategy (Sentry acquisition)