Detect Visitor.js

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

• Script sources

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

• www.visitorjs.com

Establishes

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

Does not establish

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

Can PluginView detect Visitor.js without logging in?

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

What category is Visitor.js?

Visitor.js is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Visitor.js?

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 Visitor.js?

Illustrative public indicators for Visitor.js include www.visitorjs.com. A live scan may match additional proprietary rules beyond these examples.