> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum.md).

# Connect RUM

Send real user monitoring data from your web and mobile applications to groundcover.

groundcover Real User Monitoring (RUM) captures how real users experience your web and mobile applications: sessions, interactions, network requests, errors, logs, and performance. Each SDK sends this data to your BYOC backend, where it's correlated with your backend traces, logs, and metrics.

## Choose your platform

| Platform         | SDKs                                | Guide                                                                                                    |
| ---------------- | ----------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Web applications | `@groundcover/browser`              | [Browser](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/browser.md) |
| Mobile apps      | React Native, Flutter, iOS, Android | [Mobile](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/mobile.md)   |

## Before you start

Every RUM SDK needs the same connection details. The quickest way to get them is in groundcover: open [Data Sources](https://app.groundcover.com/data-sources), select **Real User Monitoring**, and pick your platform. It fills in your `dsn` and `cluster` and gives you a setup snippet. The table below explains each value:

| Value       | What it is                                                                                                                                                                                                                                                                             |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `apiKey`    | A dedicated [ingestion key](https://docs.groundcover.com/collect-data/ingestion-keys.md) of type `RUM`. Create one under **Settings → Access → Ingestion Keys**.                                                                                                                       |
| `dsn`       | Your public groundcover endpoint, in the format `https://example.platform.grcv.io`, where `example.platform.grcv.io` is your `ingress.site` installation value. Use the origin only, with no path.                                                                                     |
| `cluster`   | The cluster name you filter RUM data by.                                                                                                                                                                                                                                               |
| `appId`     | An identifier for your application. It's reported as `service.name`.                                                                                                                                                                                                                   |
| `releaseId` | Optional. The release or version of your application. [Source maps](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/source-maps.md) are matched to stack traces by `appId` and release. Mobile SDKs fall back to the app version when it isn't set. |

Mobile SDKs also require `environment`. See [Mobile](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/mobile.md#before-you-start) for details.

## What each platform collects

| Signal           | Browser                | React Native    | Flutter      | iOS               | Android        |
| ---------------- | ---------------------- | --------------- | ------------ | ----------------- | -------------- |
| User navigation  | Pages and routes       | Yes             | Named routes | Yes               | Yes            |
| Taps and clicks  | Clicks and key presses | Yes             | Yes          | Yes               | Yes            |
| Network requests | Yes                    | `fetch` and XHR | `dart:io`    | URLSession        | OkHttp         |
| Logs             | `console`              | `console`       | `debugPrint` | Logger, swift-log | Logger, Timber |
| Errors           | Yes                    | Yes             | Yes          | Yes               | Yes            |
| Crashes          | —                      | Native builds   | Yes          | Yes               | Yes            |
| Hangs            | —                      | Native builds   | Yes          | Yes               | Yes            |
| Load performance | Page load, Web Vitals  | Native builds   | App start    | App start         | App start      |
| Frame vitals     | —                      | Native builds   | Yes          | Yes               | Yes            |
| Session replay   | Yes                    | —               | —            | —                 | —              |
| Source maps      | Yes                    | Yes             | —            | —                 | —              |

* **Native builds:** the React Native SDK captures these once its native module is compiled into your app, so they aren't available in Expo Go.
* **Platform limits:** each SDK page lists what changes setup, such as SwiftUI screens opting in on iOS. See [Browser](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/browser.md) and [Mobile](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/mobile.md).

Every SDK masks sensitive data by default. See [Browser privacy](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/browser.md#privacy-and-data-masking) and [Mobile privacy](https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum/mobile.md#privacy).

## Find your data

Once your application sends data, open [RUM](https://app.groundcover.com/rum/summary) in groundcover. Mobile apps appear when you switch the header from **Web** to **Mobile**. See [Real User Monitoring (RUM)](https://docs.groundcover.com/investigate/real-user-monitoring-rum.md) for what you can explore.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.groundcover.com/getting-started/installation-and-updating/connect-rum.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
