Quantum Metric

Overview

Quantum Metric is an enterprise digital intelligence platform used primarily by large e-commerce, financial services, and travel companies to automatically identify and quantify user experience friction points. It continuously captures session data, interaction events, and technical errors, then uses machine learning to surface anomalies and correlate UX issues with revenue impact. Customers include airlines, major retailers, and financial institutions processing millions of sessions daily.

What This Script Does

The Quantum Metric SDK is a comprehensive session recording and behavioral analytics library that operates continuously in the background.

Script Files and Domains

• cdn.quantummetric.com/qm-replay.js or a customer-specific CDN path — The primary Quantum Metric SDK. Approximately 60–120KB minified.
• Telemetry endpoint: api.quantummetric.com/v1/ or a customer-specific ingestion domain — Receives session data payloads.
• Some deployments use a first-party proxy (customer subdomain proxying to Quantum Metric) to improve data capture rates.

Cookies and Storage

• QMsession — Session identifier cookie set as a first-party cookie on the host domain. Contains a UUID identifying the current session. Expires at session end (browser close) or after 30 minutes of inactivity.
• QMvisitor — Persistent visitor ID cookie on the host domain. Contains a UUID linking sessions to a single visitor over time. Persists for 1–2 years depending on configuration.
• QMretarget — Optional retargeting cookie used when Quantum Metric is integrated with advertising platforms to link on-site behavior to ad campaigns.
• Session metadata is also maintained in sessionStorage for within-session state.

Data Collected Per Page Load

• Full DOM snapshot at page load for session replay baseline
• Page URL, referrer, page title
• Browser metadata: user agent, viewport dimensions, device type, OS, browser version
• Network conditions: connection type, effective bandwidth
• Page performance: Navigation Timing API data, resource loading waterfall

Data Collected Per Interaction (Continuous Capture)

• DOM mutations: every change to the page's rendered HTML structure is captured as a diff
• Mouse movements and clicks: position coordinates, target element, click timing
• Scroll depth and velocity
• Keyboard events: keydown timing and input field interactions (with configurable masking)
• Form field interactions: field focus, blur, and change events — field values are masked by default for sensitive fields (passwords, credit card numbers) but may be captured for other fields depending on masking configuration
• Rage clicks, error clicks, dead clicks (clicks on non-interactive elements)
• JavaScript errors: error message, stack trace, file, line, column
• Network errors: failed XHR/fetch calls with URL, method, status code, and error type
• Custom business events: cart additions, checkout steps, order completions (configured by the site operator)

ML-Powered Anomaly Detection Quantum Metric's platform analyzes aggregate session data to automatically identify: sudden increases in JavaScript errors, checkout step abandonment spikes, new form validation failures, and performance regressions. These anomalies are quantified in terms of revenue impact based on conversion rate correlation.

Consent & Compliance

Consent category: Analytics

• GDPR/ePrivacy: Quantum Metric captures detailed user interactions including mouse movements, click coordinates, form field interactions, and DOM mutations — constituting a comprehensive behavioral record of each session. The QMvisitor persistent cookie links sessions across visits, creating a persistent individual profile. This is well beyond what is necessary for operational monitoring and constitutes profiling under GDPR Article 4(4). Explicit consent is required before the SDK loads. The persistent cookie requires consent under ePrivacy regardless of GDPR legal basis.
• Session recording and data sensitivity: When deployed on financial services or healthcare websites, session data may inadvertently capture sensitive information (account numbers, health data visible on screen) despite masking configurations. Masking must be explicitly configured and regularly audited.
• CCPA/CPRA: Session recordings, click maps, and visitor behavioral profiles constitute sensitive personal information under CPRA. Opt-out rights apply. Session data shared with Quantum Metric constitutes "sharing" for analytics purposes.
• EU-US Data Privacy Framework: Quantum Metric is a US company. It relies on the DPF and SCCs for EU-to-US data transfers. EU data residency options may be available — consult with Quantum Metric directly.

Should You Block This Without Consent?

Yes. Quantum Metric captures continuous session recordings, mouse movements, form interactions, and builds persistent visitor profiles. This is detailed behavioral surveillance that requires explicit analytics consent before the SDK initializes. Even with masking enabled, the scope and persistence of data collection require prior consent under GDPR and ePrivacy.