REAL USER MONITORING

Understand every user experience

Configure the Web SDK and run the generated command on your server to start browser monitoring.

Nginx / IIS

Connect your application

Use the details of the RUM application you created in application management.

Application ID *The Web SDK applicationId Reporting method Reporting endpoint *Maps to site; enter the origin only Browser token *Use a browser Client Token, not a management API Key. Service nameserviceEnvironmentenv Application versionYour application version, independent of the Rumable package version.

Choose how to load the SDK

The server injects scripts into HTML. The browser loads and initializes the SDK using your selected method.

SDK source

The SDK is bundled with Rumable and served from your website's origin. Browsers do not need an external CDN.

Loading mode

The initialization script and SDK load asynchronously without blocking HTML parsing. Errors, requests and interactions before initialization may not be captured.

How SDK updates work

The same-origin SDK is pinned to the package. After installing a newer Rumable package, run setup or enable again for the original site to update it. Downloading or replacing the CLI alone does not update the site. Keep old assets for rollback.

Application version labels your application release. SDK remote configuration adjusts collection settings. Neither updates the SDK files.

Choose what to collect

The SDK automatically collects performance, resource and error data. Configure sampling and recording below.

Session sample rate %sessionSampleRate · 0–100Additional error session sample rate %sessionOnErrorSampleRate

Track user interactionsAutomatically record clicks and other actions · trackUserInteractions

Session ReplayRecord sessions to help reproduce the issues users encounter.

Default privacy leveldefaultPrivacyLevelSession storagesessionPersistence

Advanced Web SDK settings

Action name attributeactionNameAttributeWorker URLSame-origin URL · workerUrl Tracing URL patternsallowedTracingUrls · No tracing headers are injected when empty Tracing protocol Trace sample rate %

Mask action names Collect long animation frames Compress reporting requests (requires a Worker) Enable SDK remote configuration Share sessions across subdomains Send session cookies over HTTPS only Allow Local Storage fallback in automatic mode

Remote configuration may override static settings. setUser, custom startView and beforeSend require application code and are not implemented by server injection.

Choose your server environment

The installation command discovers websites on your server.

Server environment

Requires Bash, curl and sudo. Installation detects Linux x86 (32-bit), x64 or ARM64 automatically.

A single site is selected automatically. Choose in the terminal when there are multiple sites or URLs. If the hostname cannot be determined, you will be prompted for the URL. All paths of the selected site or application are included by default.

Advanced setup (optional)

Specify the site and paths manually

Pages need a standard <head> opening tag. Deployment checks CSP, SDK conflicts and verification pages. On incompatibility, it stops and keeps recovery records.

›_

Generate your setup command

Copy one command → Automatic setup

SDK sourceSame originLoading modeAsynchronousSession sampling100%Session replayOff

Release manifest URLUse the stable latest entry or a specific release. The manifest includes the SDK version and package checksums.

No release loaded yet. You can still configure and download TOML.

This shows the SDK version in the package. A mutable CDN may later serve a different version. Loading latest does not automatically upgrade existing sites.

Enter an application ID, reporting endpoint and browser token to generate the configuration.

After running the command

Check deployment status on your server, open the website to verify SDK execution, then confirm stored events in the receiving application.

Configuration is generated only in this browser. The command contains the browser token. Base64 is not encryption.