Real user monitoring

See what real users wait for

Instrument web, Android and iOS apps with upstream OpenTelemetry to see sessions, Core Web Vitals, errors and conversion funnels. Browser requests carry trace context into your backend, so a slow click leads to the trace behind it, and optional web session replay records pages with inputs masked.

Start free Book a demo Read the RUM setup guide

Web · Android · iOS
Core Web Vitals
Upstream OpenTelemetry

Real user monitoringacme-web · productionLast 15 minutes

Experience score0.931,195 healthy of 1,284 sessionsSessions1,284Users1,102Views5,412Error sessions37

LCP p752.1 sGoodGood up to 2.5 s

INP p75236 msNeeds improvementGood up to 200 ms

CLS p750.04GoodGood up to 0.1

Top pagesViewsLCP p75

/products/:id2,2162.0 s

/1,9041.8 s

/cart7021.9 s

/checkout5902.3 s

How it works

From an app key to a session you can replay

The SDKs are OpenTelemetry's own, and everything from sessions to funnels is worked out in your workspace from the signals they send.

01Create an appEach web or mobile app gets a public app key, its allowed origins and its replay settings.
02InstrumentAdd the upstream OpenTelemetry packages for the browser, Android or iOS. Setup gives you the code for each.
03SendTelemetry goes over OTLP/HTTP to your workspace's RUM gateway, which checks the key and scrubs personal data.
04AnalyzeSessions, Core Web Vitals, errors and frustration signals are worked out in your workspace's database.
05ConnectBrowser requests carry W3C trace context, so a slow click leads to the backend trace it started.

Sessions

Follow a session from the click to the backend trace

Every session lists its views, actions, requests, errors and frustration signals in order. Requests carry trace context, so a slow call opens the backend trace it started, with the span that waited.

Rage, dead and error clicks are found from the clicks themselves, with no extra code
JavaScript errors map back to your source with uploaded source maps, Android stacks with R8 or ProGuard mappings
Optional web session replay records the page with inputs masked by default

Anonymous userChrome 141 · macOS · Netherlands · acme-web

Duration4m 12sViews4Events38Errors0Frustration1

14:01:08View/products/:idLCP 1.7 s

14:01:52Actionclick · Add to cart

14:02:15View/checkoutLCP 2.2 s

14:02:39Actionclick · Place order

14:02:40ResourcePOST /api/checkoutTrace 4f1c9a640 ms

14:02:40Frustrationrage click · Place order ×3

14:02:41View/checkout/confirmationLCP 1.4 s

Instrumentation

Upstream OpenTelemetry on every platform

There is no Tracix SDK to adopt. Setup creates a public app key for each app and gives you the code for the upstream OpenTelemetry packages, and the RUM gateway in your workspace checks every request before it is stored.

Browser
OpenTelemetry JavaScript with web-vitals: views, LCP, INP, CLS, FCP and TTFB, resources, long tasks and errors.
Android
The OpenTelemetry Android agent: sessions, screens, app start, crashes, ANRs and slow or frozen frames.
iOS
OpenTelemetry Swift: sessions, URLSession requests, and exceptions sent as log records.
Privacy
Replay masks inputs by default, and the gateway removes email addresses and card numbers before storage.

acme-web in the browserOpenTelemetry JavaScript packages and web-vitals

OTLP/HTTP · public app key

RUM gateway in acme-prodChecks key and origin, drops bots, scrubs emails and card numbers

views, vitals, errors, actions, replay

Sessions and funnelsWorked out in your workspace's own database

Funnels and performance

Find where visitors drop out of checkout

Funnels count the sessions that pass through each step, a page view, an action or a custom event, within the window you choose, with the drop-off and the median time between steps.

Path exploration shows where visitors go next from each page
Performance breaks LCP down by page, browser, device and country
Monitors watch Web Vitals per page, JavaScript error rate and session volume

Checkout funnelWindow 30 min · last 24 hours

1./cartPage view2,410 · 100%

2./checkoutPage view1,687 · 70%−723 from the step beforemedian 41 s

3.Place orderAction1,322 · 54.9%−365 from the step beforemedian 38 s

4./checkout/confirmationPage view1,298 · 53.9%−24 from the step beforemedian 1.9 s

Better together

The user's view, joined to the systems behind it

RUM shares a workspace with your traces, synthetic tests and alerts, so a slow page leads straight to the service, network or release that caused it.

Supported platforms

What RUM collects on each platform

Every platform uses OpenTelemetry's own SDK and sends to the same RUM gateway, so sessions, errors and traces line up across web and mobile.

Platform	SDK	Sessions and performance	Errors	Trace context	Session replay
Web	OpenTelemetry JavaScript and web-vitals	Views, Core Web Vitals, resources, long tasks	JavaScript errors, symbolicated with source maps	fetch and XMLHttpRequest	Yes, inputs masked
Android	OpenTelemetry Android agent	Sessions, screens, app start, slow and frozen frames	Crashes and ANRs, symbolicated with R8 or ProGuard mappings	OkHttp	No
iOS	OpenTelemetry Swift	Sessions, requests, and screen and app-start spans you add	Exceptions as log records; no dSYM symbolication yet	URLSession	No

Native mobile screen recording is not part of the upstream OpenTelemetry mobile SDKs, so replay covers web pages only.

FAQ

Questions front-end teams ask first

Talk to an engineer

Do I need a Tracix SDK?

No. Web apps use the upstream OpenTelemetry JavaScript packages and web-vitals, with reference files Setup gives you. Android and iOS use the upstream OpenTelemetry Android agent and OpenTelemetry Swift.

Does session replay work on mobile?

No. Replay records web pages only. Android and iOS sessions, screens, crashes and requests are collected, but not screen recordings.

Can Tracix symbolicate iOS crashes?

Not yet. JavaScript errors map back to source with your source maps, and Android stacks with R8 or ProGuard mappings. iOS dSYM files can be uploaded, but they are not used to symbolicate stacks yet.

How does RUM handle personal data?

Replay masks inputs by default, with strict masking and per-element controls when you need more. The RUM gateway removes email addresses, card-like numbers and credentials in URLs before storage, and drops bot traffic.

Send your first session in minutes

Create an app key in Setup, add the upstream OpenTelemetry packages, and sessions appear as visitors arrive.

Start free Read the browser RUM guide