Detect MetricsCube

PluginView evaluates public page signals in these classes when identifying MetricsCube. Individual fingerprint rule bodies are proprietary and are not published.

• Cookies
• Script sources
• DOM selectors

Illustrative indicators derived from public catalog metadata for MetricsCube. A live scan may match additional proprietary rules beyond these examples.

• METRICSCUBE_ANALITYCS
• api.metricscube.io
• script#metricscubestats

Establishes

One or more public signals on the scanned page matched a known MetricsCube signature (3 rules) at the time of the scan.

Does not establish

A sitewide install of MetricsCube, an active vendor contract, exclusive use, or that MetricsCube is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest MetricsCube signals.
2. 2. PluginView reads only public responses (cookies, script sources, dom selectors) and scores them against the MetricsCube signature set (3 rules).
3. 3. Review the confidence score and text explanation for MetricsCube on the results page.

Can PluginView detect MetricsCube without logging in?

Yes. PluginView only reads publicly accessible responses when checking for MetricsCube — typically cookies, script sources, dom selectors. It does not bypass authentication or paywalls.

What category is MetricsCube?

MetricsCube is classified under Analytics in the PluginView directory.

How many fingerprint rules cover MetricsCube?

This reference currently tracks 3 fingerprint rules across cookies, script sources, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses MetricsCube?

Illustrative public indicators for MetricsCube include METRICSCUBE_ANALITYCS; api.metricscube.io; script#metricscubestats. A live scan may match additional proprietary rules beyond these examples.