Sentry, Bugsnag & Datadog RUM Bridge

Accelerate your engineering and QA workflows by linking front-end JavaScript exceptions directly to MousePlayer video session recordings.

1. The Problem: Stacktraces Don't Show User Context

When an unhandled JavaScript exception or network crash occurs on your website, error monitoring tools like Sentry provide dry stacktraces and browser user-agent strings. However, engineers are left asking: "What button did the user click right before the crash?" or "What data was entered into the form?"

The MousePlayer Error Tracking Bridge automatically resolves this by bridging visual replay URLs directly into your error reports. When an exception occurs, engineers can click a single link in their Sentry or Bugsnag dashboard and watch a video recording of the user's screen up to the exact millisecond of the crash.

Zero-Overhead Integration: The bridge runs silently as a background watcher inside mp.js. It detects your error tracking SDK automatically without adding measurable overhead or affecting Core Web Vitals.

2. Activation & Provider Mapping

You can enable the error tracking bridge via your dashboard interface or programmatically through our SDK configuration object.

Method A: Dashboard Activation (No-Code)

  1. Log in to your MousePlayer workspace and open Your Properties.
  2. Click the Settings / Integrations button next to your target website.
  3. In the Integrations window, toggle Sentry, Bugsnag & Datadog RUM Bridge to ON.
  4. Select your provider (sentry, bugsnag, or datadog) and click Save Changes.

Method B: Manual Script Configuration

If you prefer hardcoding the configuration, pass error_bridge_active: true inside your window.mp_config object:

<!-- MousePlayer SDK with Error Tracking Bridge Enabled --> <script> window.mp_config = { channel: 'YOUR_CHANNEL_ID', error_bridge_active: true, error_provider: 'sentry' // 'sentry', 'bugsnag', or 'datadog' }; </script>

3. Technical SDK Execution Table

Depending on your selected provider, MousePlayer executes the official JavaScript SDK tagging methods automatically:

Provider Executed JavaScript Method Injected Metadata Key
Sentry window.Sentry.setTag(...) mouseplayer_session_url
Bugsnag window.Bugsnag.addMetadata('MousePlayer', { ... }) session_url
Datadog RUM window.DD_RUM.setGlobalContextProperty(...) mouseplayer_session_url

4. Where to Find Replays in Your Error Reports

Once active, replay URLs appear instantly within your error monitoring dashboards whenever a front-end crash is logged.

Sentry Issue Details

Open any issue in your Sentry project and scroll down to the Tags section. You will see a tag named mouseplayer_session_url. You can also filter Sentry issues using the query search bar: mouseplayer_session_url:*.

Bugsnag Metadata Tabs

In your Bugsnag error report, check the bottom navigation tabs. A new custom tab named MousePlayer will appear, containing the clickable session_url hyperlink.

Datadog RUM Error Explorer

In Datadog RUM, navigate to any recorded error session and inspect the Global Context / Attributes JSON tree. The URL is indexed under @mouseplayer_session_url.

All trademarks named here belong to their respective owners. MousePlayer has no business relationship with these providers.