Skip to content
Site Qwality Site Qwality Site Qwality Docs

Session Replay quickstart

You need a RUM application with the SDK installed in your app. See the RUM quickstart.

1. Check the application’s privacy settings

Section titled “1. Check the application’s privacy settings”

New applications start on the Balanced privacy level, which masks inputs and scrubs emails, card numbers and long digit runs from page text. Strict also masks all text and blocks images and video.

  1. Go to Observe → RUM, open your application and choose Settings, then Privacy.

  2. Under Masking, check that Mask all inputs is on.

  3. Turn on Mask all text if your app displays sensitive content (financial info, PII), or pick the Strict Privacy level.

  4. Save the change from the bar that appears at the bottom.

2. Add a recording rule to enable replay

Section titled “2. Add a recording rule to enable replay”

Replay activates when a session matches a Replay recording rule. A new application already has one, Errored sessions, which replays every session with an error, so you can skip this step. If you deleted it, open the application’s Recording rules page, click New recording rule, name it Errored sessions, choose Replay, add an Error condition, then click Preview rule and Save rule. Or through the API:

Terminal window
curl -X POST "https://api.siteqwality.com/rum/$APP_ID/rules" \
  -H "Authorization: Bearer $SITEQWALITY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Errored sessions",
    "capture": "replay",
    "conditions": [{ "kind": "error" }]
  }'

A new rule reaches new page loads within 6 minutes; see how long changes take.

3. Trigger an error in your app

Section titled “3. Trigger an error in your app”

Open your app and do something that throws an error, or temporarily add throw new Error('replay test') to a button handler and click it.

Because an error rule could match any session, the recorder has been buffering since the page loaded, so the replay includes up to the last 60 to 120 seconds before the error. Keep using the page for a few seconds; segments upload within about 20 seconds, or when you leave the page.

4. Watch the replay

Section titled “4. Watch the replay”

  1. In RUM → Sessions, find your session (it has the error indicator).

  2. Click the play button on its row to open the player. From the error’s page under RUM → Errors, Open full replay opens the same replay at the error.

  3. Press play, and jump to the error with its marker or Next error (E).

Privacy checklist

Section titled “Privacy checklist”

Before rolling out replay broadly:

  • The application has a privacy level. An application on Custom with mask_inputs: false records input values.
  • Sensitive text (PII, financial figures, health info) is covered by mask_selectors, or the application is on Strict.
  • Payment forms match a block_selectors entry (not recorded at all), and pages that should never be recorded are in never_record_urls.
  • Your privacy policy mentions session replay if you collect from EU/CA customers (GDPR/CCPA).
  • Replay rules are scoped to the sessions you need, not every session.

What’s next

Section titled “What’s next”
Recording rules More rule patterns.
Replay overview What's captured, retention, pricing.

Privacy Cookie preferences