Detect WiserNotify

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

• JavaScript globals
• DOM selectors

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

• wiser
• link

Establishes

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

Does not establish

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

Can PluginView detect WiserNotify without logging in?

Yes. PluginView only reads publicly accessible responses when checking for WiserNotify — typically javascript globals, dom selectors. It does not bypass authentication or paywalls.

What category is WiserNotify?

WiserNotify is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover WiserNotify?

This reference currently tracks 2 fingerprint rules across javascript globals, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses WiserNotify?

Illustrative public indicators for WiserNotify include wiser; link. A live scan may match additional proprietary rules beyond these examples.