Detect Pocus

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

• Script sources

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

• pocustrack.com/pocus.js

Establishes

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

Does not establish

A sitewide install of Pocus, an active vendor contract, exclusive use, or that Pocus 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 Pocus signals.
2. 2. PluginView reads only public responses (script sources) and scores them against the Pocus signature set (1 rules).
3. 3. Review the confidence score and text explanation for Pocus on the results page.

Can PluginView detect Pocus without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Pocus — typically script sources. It does not bypass authentication or paywalls.

What category is Pocus?

Pocus is classified under Marketing automation in the PluginView directory.

How many fingerprint rules cover Pocus?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Pocus?

Illustrative public indicators for Pocus include pocustrack.com/pocus.js. A live scan may match additional proprietary rules beyond these examples.