Quantum Metric review

Quantum Metric is a hosted experience-analytics platform, not a library, CLI, or self-hosted server. It captures behavioral, technical, experience, and business context across digital journeys so teams can investigate where customers struggle and what changes may be worth making.

In a typical stack, it sits alongside customer and system data sources such as a CRM, CDP, data warehouse, APM, or logs. The vendor describes observed channels including web, app, kiosk, direct, voice of customer, and call center. Felix analytics groups sessions around issues, identifies likely causes, and suggests next actions. Revenue-impact features rank issues by revenue at risk and compare outcomes against a control or matched cohort. The platform also connects experience context to AI and support tools through MCP. That makes it an analysis and context layer for product, engineering, marketing, and support teams, rather than a replacement for their existing data stores or monitoring systems.

The vendor names MCP as the connection surface for bringing experience context into tools used for analysis, development, and customer support. Its homepage lists ChatGPT, Claude, Gemini Enterprise, and Microsoft Copilot for analysis, plus Devin, Factory.ai, Cursor, Claude Code, Codex, and GitHub Copilot for building and improving software. These are presented as MCP connections; confirm the exact supported clients, setup steps, and permissions with Quantum Metric.

The vendor does not publish a language-specific SDK list or API contract on its homepage. It also does not name a CLI or webhook integration there. Before implementation, confirm in the vendor’s docs whether your stack needs browser or app instrumentation, which languages and SDK versions are supported, and how authentication, event ingestion, data access, and rate limits work. The site describes experience capture and MCP context sharing, but does not give enough implementation detail to estimate engineering effort from the integration surface alone.

Quantum Metric’s listed plan is Enterprise, with custom pricing for large digital-property teams. The vendor publishes no starting price, monthly or annual rate, free plan, or free-trial terms. Session limits are set by agreement, and the pricing page says data collection continues beyond those limits. It also says there are no wasted seats, but does not publish the commercial details behind that statement.

The bill may include product add-ons, professional services, and AI consumption add-ons; their prices are not published. Overage rates are also not published. That leaves the key production cost questions—session allowance, treatment of sessions beyond the limit, and AI consumption billing—to resolve with sales before rollout. Ask for a worked estimate based on your expected traffic, number of properties, retention needs, and planned AI usage. Without a published rate card or usage formula, we can’t compare the total cost with a per-event analytics product or forecast spend from public prices.

Quantum Metric is presented as a hosted platform. The vendor does not publish an open-source licence or a self-hosting offer, so teams that require source access or deployment inside their own infrastructure should confirm availability directly before evaluation. Do not assume you can run the collection or analytics stack on your own servers.

The vendor also does not publish data-export terms on its pricing information. Ask what raw and processed data can be exported, in which formats, at what frequency, and whether session replay assets and annotations are included. Migration effort will depend on those answers and on how much your workflows rely on Felix analyses, session context, and MCP connections. If you leave, plan to preserve the event and business metrics needed to reproduce your reporting elsewhere. Confirm retention, export access, and contract-end procedures in writing before building operational dependencies around the platform.

The vendor sets session limits by agreement and says collection continues beyond those limits. It does not publish overage rates, so clarify whether continued collection affects billing, access, or reporting when a limit is reached. The homepage describes linking surveys to sessions, separating human and agent activity, and sharing context with AI and support tools; confirm the controls and data flows that apply to your deployment.

Before relying on the platform for production diagnosis, ask about ingestion and query limits, service availability commitments, data retention, access controls, and security and compliance documentation. The vendor does not publish those details alongside its plan information. Also confirm how instrumentation behaves across web and app releases and what happens if capture or MCP connections are unavailable. A Reddit thread contains one commenter’s brief positive endorsement and a second commenter’s explicit competitor affiliation; it offers little evidence about reliability or support at scale. Treat those questions as part of procurement, not assumptions.