Quantum Metric
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Quantum Metric Inc. · www.quantummetric.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Quantum Metric at a glance
- Vendor
- Quantum Metric Inc.
- Headquarters
- Incorporated in the United States source, captured 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Quantum Metric 2/5, the mean of 6 judges. The judges score Quantum Metric as an experience-analytics platform — session replay, automatic struggle detection, real-user monitoring, funnels — not a testing engine: experimentation scope lands at 0-1 and statistical rigour at 0, with no public information on traffic splitting, variant delivery, editors or statistical method. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The judges score Quantum Metric as an experience-analytics platform — session replay, automatic struggle detection, real-user monitoring, funnels — not a testing engine: experimentation scope lands at 0-1 and statistical rigour at 0, with no public information on traffic splitting, variant delivery, editors or statistical method. Its strongest result is performance impact, an even 6, built on unusually candid figures: a 70-80 KB asynchronous web tag loaded once per session, deferred processing, and a stated 8-9% decrease in mobile frames per second. Data and integrations spreads from 5 to 7: a documented API with 16 capability areas and a 120-second query limit, plus a two-way Tealium integration, while the BigQuery warehouse is the vendor's with no public information on visitor-level raw export. Sovereignty splits between 3 and 4 as judges weigh standard contractual clauses, Data Privacy Framework certification and a subprocessor list against a Colorado contracting entity, "any country" processing language and US subprocessors Anthropic and OpenAI. Consent and tracking holds at 2 — strong device-side controls, nothing public on consent sequencing; pricing transparency sits at 1-2 beyond a Pricing Plans page.
Speaks for it
- Performance impact scores an even 6 on published figures: a 70-80 KB asynchronous web tag, loaded once per session and browser-cached, with processing deferred until the page is ready.
- Unusually candid mobile disclosure — stated SDK sizes (about 200 KB on Android, 1 MB on iOS) and an admitted 8-9% decrease in mobile frames per second.
- A documented API across 16 capability areas with bearer-token authentication, defined error codes and a stated 120-second query timeout, plus a two-way real-time Tealium integration into AudienceStream.
- Device-side privacy controls — Capture, Do Not Capture or Encrypt per data point, passwords and card fields blocked by default, pseudonymization under a customer-only private key, and audit-logged re-identification.
- Experience-analytics depth — session replay, automatic struggle detection, funnels and friction points quantified in dollar figures.
Held against it
- Experimentation scope scores 0-1 — we found no public information on traffic splitting, variant delivery, an experiment editor or server-side experiment SDKs.
- Statistical rigour scores 0 — we found no public information on any statistical method, confidence interval, sample-size guidance or sample-ratio-mismatch detection.
- Consent questions stay open — no public information on when the tag runs relative to consent, consent-management-platform integrations, or the cookies and storage keys it sets.
- Sovereignty scores 3-4 — the contracting entity is Quantum Metric, Inc. of Monument, Colorado, the privacy policy allows storage and processing in any country where the company has facilities, US subprocessors Anthropic and OpenAI handle Customer Data, and EU hosting of visitor data is not stated as standard.
- The petabyte BigQuery warehouse is the vendor's — we found no public information on visitor-level raw export to a customer's own warehouse.
Best for
- You need to understand why visitors struggle — session replay, funnels and automatic struggle detection ranking friction by its dollar impact.
- You already run A/B tests in another tool and want analytics around the programme, from generating hypotheses to analysing test results.
- Your team builds internal tooling and wants a documented API to query sessions, run funnels and execute saved queries.
- You run Tealium and want real-time customer-experience data streaming into AudienceStream for personalisation and retargeting.
Avoid if
- You need one platform to run the experiments themselves — traffic splitting, variant delivery, a visual or code editor, or experiment SDKs.
- You must show your legal team a documented consent sequence, a consent-management-platform integration or a published cookie and storage-key list before deployment.
- You require EU residency for visitor data as a standard term, or a subprocessor chain without US-based processors handling Customer Data.
- You need to export visitor-level raw data to your own warehouse for independent re-analysis of results.
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 0 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 3 of 5 |
| Analytics, data export & integrations | 3 of 5 |
| European sovereignty | 2 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The documented product is a digital experience analytics platform — session replay, struggle-detection algorithms, real user monitoring and funnels — and the experimentation pages I read are tours on generating hypotheses and analysing A/B test results, which feeds a testing programme rather than running one. I found no public information on a visual editor, traffic splitting, variant delivery or audience targeting, so on this evidence I could not run my testing programme on it. 1 5 6 8
The E-Commerce Manager
Every captured page describes an experience-analytics platform — session replay, automatic struggle detection, real-user monitoring, funnels — and the experimentation content is a product tour on generating hypotheses plus another on analysing A/B testing results, which sits around tests run elsewhere. We found no public information on traffic splitting, variant serving, a visual or code editor, or server-side SDKs for experiments. 5 6 8
The Product Engineer
This is a session-replay and real-user-monitoring platform — struggle detection, funnels, replay, Core Web Vitals — not something that serves variants. The only experiment-adjacent material is a product tour on generating hypotheses and one on analysing A/B test results, and the personalisation in the captured integration story is done downstream by Tealium, not here. I found no public information on traffic splitting, variant delivery, feature flags, or server-side experimentation SDKs. 1 5 6 9
The CRO Consultant
The captured pages show a session-replay and real-user-monitoring platform — struggle detection, funnels, replay, core web vitals — and the two experiment-themed pages in the capture are about generating hypotheses and analysing A/B test results. We found no public information on traffic splitting, variant delivery or an editor for serving changes, so for my clients this reads as the measurement stack around a testing programme rather than the platform that runs it. 1 5 6 8
The Data Protection Officer
The captured product pages document a session-replay, struggle-detection and real-user-monitoring platform with funnels and friction quantified in dollar figures. The vendor's product-tour library carries pages on generating experimentation hypotheses and analyzing A/B testing results, but we found no public information on splitting traffic, serving variants, a visual editor or experiment SDKs, so the documented product reaches only the analytics end of the scale. 1 5 6 8
The Skeptic
What the captured pages document is an experience-analytics platform: real-user monitoring, automatic struggle detection, session replay, funnels and voice-of-customer surveys. We found no public information on splitting traffic or serving variants — not even on the two captured product-tour pages about generating experimentation hypotheses and analysing A/B-test results — so at the documented level this observes behaviour rather than testing it. 1 5 6 8
Statistical method & guardrails
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead not rated — no public information
I found no public information on how a winning variant would be decided — no named statistical method, no significance or interval reporting, no sample-size guidance, and nothing on peeking, multiple comparisons or sample ratio mismatch — on the experimentation product-tour pages or anywhere else I read. 5 6 8
The E-Commerce Manager not rated — no public information
We found no public information on the statistics that decide a winner: no method is named and no confidence intervals, sample-size guidance, peeking protection or sample-ratio-mismatch detection appears on the captured pages, including the product tour on analysing A/B testing results. 5 6
The Product Engineer not rated — no public information
I found no public information on how a winner would be decided — no named method, confidence or credible intervals, sample-size guidance, peeking protection or sample ratio mismatch detection appears in the captured pages, including the product tour on analysing A/B testing results. 5 6
The CRO Consultant not rated — no public information
We found no public information on any statistical method on the captured pages — no named method, intervals, sample-size guidance, or protections such as sample-ratio-mismatch detection, including on the pages about experimentation hypotheses and analysing A/B test results. 5 6 10
The Data Protection Officer not rated — no public information
We found no public information on how results are evaluated statistically. The captured product-tour pages on analyzing A/B testing results and generating experimentation hypotheses yielded no confirmed facts on the method, intervals, peeking, multiple comparisons or sample ratio mismatch, so this cannot be scored from what was captured. 5 6
The Skeptic not rated — no public information
We found no public information on the statistics behind any testing capability: no method named, no significance or probability figure, no sample-size or duration guidance, and nothing on peeking, multiple comparisons or sample-ratio checks. The two captured pages on A/B-test analysis document no methodology I can evaluate. 5 6
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
The security pages document genuine on-device controls — capture set to Capture, Do Not Capture or Encrypt, passwords and card fields blocked by default, and pseudonymisation with a decryption key only the customer holds — alongside GDPR assistance. But I found no public information on when the tag fires relative to consent, integration with consent management platforms, or the cookies and storage keys it writes, which is exactly what my legal team will ask under §25 TDDDG. 2 3 7
The E-Commerce Manager
The privacy pages do document device-side controls — Capture, Do Not Capture or Encrypt, with passwords, credit cards and CVV2 fields blocked by default and pseudonymisation separating PII from analytical data — and the web tag is described as asynchronous, loaded once per session and held in the browser cache. But we found no public information on when the tag runs relative to consent under §25 TDDDG, any consent-management-platform integration, or a published list of the cookies and storage keys it sets. 3 7
The Product Engineer
What is documented is data minimisation, not consent sequencing: three capture options (capture, do not capture, encrypt), sensitive fields blocked by default, pseudonymisation with a customer-held private key, and audit-logged re-identification. I found no public information on holding the tag until consent, consent-platform integrations, or a published list of the cookies and storage keys it sets on the device. 3 7
The CRO Consultant
The privacy and security pages document three capture options — capture, do not capture, encrypt — configured on the end user's device, default blocking of password and card fields, and pseudonymization with a customer-held key the vendor states it cannot use, which is a real story for a DPO. But we found no public information on when the script runs relative to consent, on consent management platform integrations, or on the storage keys and identifiers the tag sets, so I could not clear it against §25 TDDDG from the captured pages. 2 3 7
The Data Protection Officer
The vendor documents on-device capture options (Capture, Do Not Capture, Encrypt), default blocking of passwords and payment fields, pseudonymization with a customer-only private key, audit logging of every re-identification, and a general claim of helping customers with GDPR. We found no public information on whether the tag runs before the consent banner is answered, on a consent-pending mode, on consent management platform integration, on §25 TDDDG guidance, or on the cookies and storage keys the tag sets. 2 3 7
The Skeptic
The privacy pages document real device-side controls — Capture, Do Not Capture or Encrypt per data point, with passwords and card fields blocked by default — and pseudonymization under a key only the customer holds. We found no public information on when the tag runs relative to consent, on integrations with consent management platforms, on the cookies and storage keys the tag sets, or on how testing maps to the German ePrivacy rules. 3 7
Snippet performance & flicker
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead
They publish real numbers rather than adjectives: a 70-80 KB tag loaded asynchronously once per session and cached, processing deferred until the page is interactive, data compressed and sent in small batches, mobile SDKs at about 1 MB for iOS and 200 KB for Android, and an honest 8-9% decrease in mobile frames per second. I found no public information on the web tag's measured impact on Core Web Vitals, or on a self-hosting or first-party delivery option, so I hold this at the level the published figures support. 7 8
The E-Commerce Manager
Concrete and unusually honest numbers are published: a 70-80 KB asynchronous web tag loaded once per session and cached across pages, processing deferred until the page is interactive, compressed data sent in small frequent batches off the main thread, stated SDK sizes, and a stated 8-9% decrease in frames per second for mobile apps. The platform measures Core Web Vitals on customers' pages, though we found no published figure for the tag's own effect on them, nor self-hosting or per-project bundles. 7 8
The Product Engineer
Unusually honest disclosure: the web tag is stated at 70-80 KB, asynchronous, loaded once per session and cached, sending compressed data in small frequent batches off the main thread; mobile SDK sizes are published along with an admitted 8-9% drop in frames per second. Core Web Vitals are measured on the customer's site, though — I found no published figures for the tag's own effect on those vitals, and no self-hosting or first-party-domain option. 7 8
The CRO Consultant
The vendor publishes real overhead numbers rather than adjectives: the web tag is stated at 70-80 KB, asynchronous, loaded once per session and browser-cached, deferring processing until the page is ready, with compressed data in small batches and no main-thread blocking, and mobile SDK sizes come with a stated 8-9% decrease in frames per second. We found no public information on the tag's measured impact on Core Web Vitals, a self-hosting option, or per-project bundles, which is what the top of this scale asks for. 7 8
The Data Protection Officer
Published figures are unusually concrete: the web tag is 70-80 KB, loads asynchronously once per session, is browser-cached, defers processing until the page is interactive, and sends compressed data in small frequent batches; the vendor even discloses an 8-9% decrease in mobile frames per second with SDK sizes of about 200 KB on Android and 1 MB on iOS. We found no public information on a self-hosting or first-party-domain option, per-project bundles, or the tag's own measured effect on Core Web Vitals. 7 8
The Skeptic
Published figures exist and some are unusually candid: a 70-80 KB web tag loading asynchronously once per session and cached, processing deferred until the page is ready, data batched and compressed off the main thread, sized mobile SDKs, and a stated 8-9% frames-per-second decrease in mobile apps. We found no public information on the tag's measured effect on Core Web Vitals, on self-hosting or first-party delivery, or on per-project bundles, which caps this below the top band. 7 8
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
The Tealium partnership pushes customer-experience data into AudienceStream in real time for audiences, personalisation and retargeting, and the MCP server is a genuinely documented API — bearer-token authentication, a 120-second query limit, and tools to run funnels, saved queries and session investigations. I found no public information on exporting visitor-level raw data or streaming results into our own warehouse; the petabyte BigQuery warehouse described is the vendor's, not the customer's. 7 9 10
The E-Commerce Manager
Getting data out is well served by documented routes: a Model Context Protocol server with bearer-token auth covering sixteen tool areas including running funnels and saved queries, stated limits such as analytics queries capped at 120 seconds, and a two-way Tealium integration streaming customer-experience data to AudienceStream for personalisation and retargeting. Google BigQuery serves as the data warehouse with petabyte-scale querying; we found no public information on visitor-level raw export or integration with Google Analytics, Adobe Analytics or GTM. 7 9 10
The Product Engineer
The MCP endpoint is a genuine API — tools across sixteen capability areas, bearer tokens, error codes, a stated 120-second query limit, and access to funnels, saved queries and session replay URLs — the kind I could build internal tooling on, and a two-way Tealium integration feeds AudienceStream for audiences and personalisation. But the BigQuery warehouse is the vendor's, not mine: I found no public information on exporting visitor-level raw data to a customer's own warehouse. 7 9 10
The CRO Consultant
Getting data out is genuinely documented: a two-way Tealium integration feeding AudienceStream in real time for personalisation and retargeting, in-platform querying described at petabyte scale on the vendor's Google BigQuery warehouse, and a documented API over the Model Context Protocol covering ad-hoc analytics queries, saved queries, funnels, sessions and dashboards with stated limits such as a 120-second query timeout. We found no public information on named Google Analytics or Adobe Analytics connectors, or on visitor-level raw export to a customer's own warehouse, which is what I need to re-check a result in a client's own data. 7 9 10
The Data Protection Officer
A two-way Tealium integration is documented, including real-time customer-experience data sent to AudienceStream for personalization and retargeting, and a Model Context Protocol API is documented end to end with bearer tokens, a 120-second query limit and error codes, covering ad-hoc analytics queries, funnels, sessions and replay URLs; Google BigQuery is named as the warehouse. We found no public information on bulk visitor-level raw data export or warehouse-native analysis on the customer's own metrics. 7 9 10
The Skeptic
There is a genuinely documented API — a Model Context Protocol endpoint with bearer-token authentication, sixteen tool areas covering sessions, funnels, dashboards and alerts, and stated limits such as a 120-second query timeout and defined error codes — alongside a real-time integration with the Tealium customer data platform. We found no public information on exporting visitor-level raw data into the customer's own warehouse or on Google Analytics, Adobe or tag-manager integrations; the petabyte BigQuery warehouse described is the vendor's, not the customer's. 7 9 10
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
The contracting entity is the US company in Colorado, the privacy policy states personal information may be stored and processed in any country where they have facilities, and the published subprocessor list shows Google, Anthropic and OpenAI in the United States handling customer data, with the Data Privacy Framework and standard contractual clauses as the stated safeguards. EU affiliates in Germany and Spain appear for professional services and a UK representative is named, but I found no public information stating EU hosting of visitor data as standard. 2 3 4
The E-Commerce Manager
The contracting entity is Quantum Metric, Inc. of Colorado, USA, and the privacy policy states personal information may be stored and processed in any country where the company has facilities; transfer safeguards are stated through EU-US, UK and Swiss Data Privacy Framework certification and standard contractual clauses, with a UK representative and German and Spanish affiliates on the subprocessor list. We found no public information confirming EU hosting of visitor data as standard — hosting is Google Cloud in the region closest to the customer, and the subprocessor list includes US companies (Google, Anthropic, OpenAI) processing Customer Data. 2 3 4
The Product Engineer
The contracting entity is Quantum Metric, Inc. of Monument, Colorado; personal information may be stored and processed in any country where the company has facilities; and the published subprocessor list includes US processors handling customer data. EU-US Data Privacy Framework certification and standard contractual clauses are stated as transfer safeguards, but I found no public information on EU hosting or residency for the visitor data the tag collects. 2 3 4
The CRO Consultant
The contracting entity is Quantum Metric, Inc. of Colorado with a UK-based EU representative, a subprocessor list is published with locations — Google for hosting in the United States, EU and other locations as agreed, plus Anthropic and OpenAI in the US handling Customer Data — and standard contractual clauses with Data Privacy Framework certification are stated. We found no public confirmation of EU hosting as standard: the privacy policy says personal information may be stored and processed in any country where the vendor has facilities, while the security page places data at rest in the Google region closest to the customer. 2 3 4
The Data Protection Officer
The contracting entity is Quantum Metric, Inc. of Monument, Colorado, with a representative named in the UK, and the privacy policy states personal information may be stored and processed in any country where the company has facilities, backed by EU-US Data Privacy Framework certification and standard contractual clauses. A subprocessor list is published with locations and names Google for hosting alongside US-based Anthropic and OpenAI processing customer data, but visitor-data residency is not confirmed on the captured pages and EU processing is not stated as standard. 2 3 4
The Skeptic
The contracting entity is Quantum Metric, Inc. of Colorado, the privacy policy states personal information may be stored and processed in any country where the company has facilities or engages providers, and US subprocessors including Anthropic and OpenAI handle Customer Data. Credit where due: standard contractual clauses and Data Privacy Framework certification are stated, a subprocessor list with locations is published, hosting runs on Google Cloud with encryption in the region closest to the customer, and German and Spanish affiliates process customer data in Europe — but EU processing of visitor data is not stated as standard, and the named EU representative sits in the United Kingdom. 2 3 4
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
A pricing plans page exists on the site, but I found no public information on any price figure, tier structure, or the traffic metric and its limits behind a tier. Neither I nor finance could begin to compute an annual cost from the public pages I read. 1
The E-Commerce Manager
The homepage links a "Pricing Plans" page, so pricing exists as a public page, but no tier price, billing period, traffic metric or its limits is confirmed in the captured material — a shop like mine cannot estimate what the December bill would be from what is public. 1
The Product Engineer
The only pricing material captured is a Pricing Plans link on the homepage. I found no public information on tier prices, the traffic metric behind them, overage rates, seats, or minimum term, so a buyer cannot estimate the real annual cost from what was captured. 1
The CRO Consultant
In a category priced on traffic I need one number I can estimate against, and the only pricing fact captured is that a Pricing Plans page exists on the site. We found no public information on tier prices, the traffic metric behind them, seats, term or overage, so an annual cost cannot be worked out from the captured pages. 1
The Data Protection Officer
A pricing plans page exists on the vendor's site, but the captured pages show no price figures, traffic metric, billing period or tier structure. A buyer cannot estimate the annual cost from the public information captured. 1
The Skeptic
The vendor's site shows a Pricing Plans page, but the captured pages document no price, no tiers, no traffic metric such as sessions or visitors, no billing period and no seat counts. A buyer can compute nothing from what is public here. 1
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in US | 0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Quantum Metric
Is Quantum Metric European?
Not determined: the vendor’s pages as captured do not say where Quantum Metric is based. Its vendor, Quantum Metric Inc., is incorporated in the United States, per the vendor’s page captured 17 Nov 2026.
Where does Quantum Metric store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Quantum Metric have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Quantum Metric?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Quantum Metric alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 49 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.quantummetric.com Checked 17 Nov 2026 Details →
- 2 Legal notice — found from the homepage www.quantummetric.com Checked 17 Nov 2026 Details →
- 3 Privacy policy — found from the homepage www.quantummetric.com Checked 17 Nov 2026 Details →
- 4 Subprocessor list — found from the homepage www.quantummetric.com Checked 17 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →
- 6 Experiment types & delivery — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →
- 7 Snippet performance & flicker — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →
- 8 Snippet performance & flicker — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →
- 9 Analytics, data export & integrations — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →
- 10 Analytics, data export & integrations — found from sitemap www.quantummetric.com Checked 17 Nov 2026 Details →