Skip to main content

Quick Start

Create one web application, install the snippet, confirm a session, and save one experience policy.

Prerequisites​

  • Your account can create RUM applications and open setup.
  • You can change the frontend build or page template.
  • Browsers can reach the collection endpoint. Allow the page origin on the application.

Create the application and install the snippet​

  1. Open Integration → Applications and create an application.
  2. Open Integration → Setup and continue into that application's steps.
  3. Copy the snippet for npm, React, CDN, or the generic fragment.
  4. Put it in the application entry. CDN and generic fragments belong early in page load. Follow the npm or React instructions on the page for the package and initialization.
  5. Allow the site origin so other sites cannot write into this application.
  6. Open the site in a real browser and click or navigate once.

UI Guide:

Screenshot to be added.

  • What to check: Status is Connected when both the latest accept time and store time are within 15 minutes. No fresh data means Not connected. A turned-off application is Disabled.

Confirm sessions and page metrics​

  1. Open Experience → Sessions, then choose the application and time range.
  2. Confirm the visit is listed. Sort by Impact, Start time, Errors, or Duration, or search by session id.
  3. Open a session for pages, device, and browser. Open replay when you need the interaction.
  4. Open Experience → Views & performance for LCP, INP, and the distribution. An empty metric means there is no sample. It does not mean the page is healthy.

Check errors and releases​

  1. Open Quality → Errors and open a grouped error to see the evidence stack.
  2. If the stack is minified, open Quality → Releases and switch to Source maps.
  3. Choose the application, enter the release and deployed artifact path, and upload the source map. All four are required.
  4. Rotate the CI token if a pipeline will upload maps. The token is shown once. Copy it before closing the dialog.
  5. Select a single application before marking an experience baseline. The all-application summary cannot mark one.

Create one policy​

  1. Open Events → Policies and choose the application.
  2. Choose a metric: error rate, LCP P75, INP P75, CLS P75, FCP P75, TTFB P75, or session count.
  3. Choose a comparator and fill warning and critical thresholds. Error rate is a percentage, CLS is a score, and timing metrics are milliseconds. The form suggests common defaults. Session count has none.
  4. Choose Info, Warning, or Critical. Save, then enable or disable the policy in the list.
  5. Open Events → Alerts after the metric crosses the threshold.

Optional: funnel and erasure​

  1. Open Experience → Funnels and create a funnel. The name is required. Provide 2 to 8 routes separated by commas, such as /,/checkout,/success.
  2. Bind an application if you want the funnel limited to it. Conversion uses the current filters.
  3. To erase one user, open Governance → Compliance erase, choose the application and user id, submit, and check the job list.

Verify​

  • Setup shows Connected, and Sessions shows the visit.
  • Views show page metrics where samples exist.
  • A forced frontend error appears in Errors. The matching source map moves the stack closer to source.
  • An enabled policy creates an alert when the threshold is crossed.