Skip to main content
An application is the website or the app that sends RUM events. Create it before any SDK sends data: the client token is bound to one application, and MoleSignal refuses an event for an application that does not exist. Open RUM → Applications to list the applications of the workspace. Creating, changing, and deleting an application requires api_tokens.manage, because an application comes with its client token. Reading the list requires streams.query.

​
Create an application

1

Open the form

Click Create application. A workspace without an application shows the same button on the explorer.
2

Name the application

Enter a Name of up to 128 characters that no other application uses, such as Checkout web, and choose the Platform: Browser, Android, iOS, Flutter, React Native, or Other. The platform decides which setup snippet the application shows and nothing else: an event says by its source what sent it.
3

Decide the identifier

The Identifier is the value SDKs are configured with as applicationId. Leave it blank to make it from the name (checkout-web) or type one of up to 64 characters from A-Z, a-z, 0-9, ., _, :, and -. The identifier cannot change after the application is created.
4

Click Create

The application opens with its client token.
Creating an application also creates the seven RUM streams of the workspace when they do not exist yet.

​
Client token

Open an application to see its Client token. The token has the form msrum_<prefix>_<secret>, never expires, and holds only rum.write for this application. It is shown masked. Select Show the token or Copy the token.
The token ships inside browser and mobile code, where users can read it. Use only this token in client code, and never an owner, administrator, or personal token. Deleting the application revokes the token.
The same token is available from the API. Open the setup guide in the application opens the Datasource guide of the platform with the application chosen: the guide shows the endpoint, the token, the SDK snippet filled in with the identifier, and a check that data arrives. React Native and Other have no guide: send the events with the token directly.

​
Collection

The settings of an application decide what is kept with each event. Change them in the application and click Save. A change applies to events that arrive after it. Data already stored does not change.

​
Sensitive data and sessions kept

Sensitive data has a switch for each kind of text the server takes out of an event before it is stored: tokens, keys, and passwords; email addresses; phone numbers; payment card numbers; identity numbers; and the values of sensitive URL parameters. All are on by default. See RUM privacy for what each takes out. Sessions kept says which sessions the application stores. Share of sessions kept (%) keeps that share of the sessions the application receives, a whole number from 0 to 100, and a session is kept or dropped as a whole, its replay included. Add a filter gives the sessions it describes (by environment, version, country, browser, and the like) a share of their own, the first filter that describes a session deciding; the share of the others is then Share of the other sessions kept (%). Keep every error stores the errors of the sessions that are not kept all the same. Pages that show totals scale what was kept up to every session and say Estimated. See RUM data sampling.

​
Issues

The Issues section sets how many new issues the application opens in an hour.

​
Delete an application

Click Delete application and confirm. The client token stops working at once, and SDKs that use it are refused. The events the application already sent stay in the streams until their retention ends them, and remain searchable in the explorer.

RUM event format

The events a client sends with the token.

Browser RUM SDK

Configure the SDK with the identifier and the token.
Last modified on October 26, 2026