Detect Webpushr

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

• JavaScript globals
• Inline scripts

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

• WebPushr.notificationCard
• webpushr_display_button
• cdn.webpushr.com/app.min.js

Establishes

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

Does not establish

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

Can PluginView detect Webpushr without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Webpushr — typically javascript globals, inline scripts. It does not bypass authentication or paywalls.

What category is Webpushr?

Webpushr is classified under Marketing automation in the PluginView directory.

How many fingerprint rules cover Webpushr?

This reference currently tracks 3 fingerprint rules across javascript globals, inline scripts. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Webpushr?

Illustrative public indicators for Webpushr include WebPushr.notificationCard; webpushr_display_button; cdn.webpushr.com/app.min.js. A live scan may match additional proprietary rules beyond these examples.