Digital experience: real users, synthetic journeys, session replay and mobile apps
Know how pages and apps feel to the people using them, and catch a broken journey before they do - with every slow request opening into the trace and the host behind it.
See what your users see
Infrastructure that is green can still deliver a slow or broken experience. Rapitt measures it from both ends: real visitors and real phones report how pages and screens behave, and scheduled journeys check the paths that matter before anyone complains.
Browser and mobile requests carry a W3C trace identifier to your backend, so a slow page opens straight into the trace of the request behind it.
Four ways of watching
Each one stands alone; together they close the loop between the user and the server.
Real user monitoring
One script tag. Page views and route changes in single-page apps; Core Web Vitals (LCP, INP, CLS) with TTFB and FCP; JavaScript errors with stacks; request timings linked to traces. Broken down by page, browser, device, operating system, country and connection.
Synthetic journeys
Scheduled browser journeys (open, click, type, select, wait, check text or address, screenshot) and API steps with values passed between steps. Per-step timings, the failing step and why, screenshots and Web Vitals. From the cloud or from inside a client network.
Session replay
Watch a visit as it happened, opened from an error or a slow request. Opt-in and sampled, inputs masked by default, passwords never recorded, block selectors, every viewing audited. Web pages only.
Mobile app monitoring
SDKs for Android, iOS and hybrid apps (Capacitor, Ionic, Cordova, React Native). Crashes grouped by cause, releases, screens, network calls, sessions, crash-free sessions and users, and freeze detection.
Privacy is part of the design
The browser script sets no cookies and stores no IP address. Replay masks what people type before it leaves the browser and refuses to record a password. Mobile SDKs read no device identifier, only a random install identifier, and strip query strings from what they report.
These choices are written in the privacy notice, so they can be checked rather than taken on trust.
What you get for each user problem
A visitor reports a slow checkout: open the RUM sample, follow its trace into the backend, see the host and the database call, and, if replay was on for that session, watch it. A scheduled journey fails at step four at 03:10: the screenshot, the timing and the error are on the run, and an alert goes out on the channels you chose.
Digital experience questions
Does the browser script use cookies?
No. It uses no cookies and no local storage, only a per-tab identifier in session storage. IP addresses are not stored, and query strings and fragments are removed in the browser.
Does session replay record what people type?
Not by default. Input, textarea and select values are masked, password fields are never recorded, and you can block any element. A strict mode hides all text. Replay is switched off until you turn it on, only a share of sessions are recorded, and every viewing is audited.
Can a synthetic journey test something inside a client network?
Yes. A journey can run from the cloud or from inside a named VPN through its tunnel, so an internal portal is tested from where its users are.
Is there replay for mobile apps?
Replay is for web pages. Mobile apps are covered by crash, release, screen, network and session monitoring.
See it on your own systems
A walkthrough runs on your own estate. Reserve your workspace address while you book.