Detect AutoManager

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

• Script sources
• DOM selectors

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

• .automanager.com/
• link

Establishes

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

Does not establish

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

Can PluginView detect AutoManager without logging in?

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

What category is AutoManager?

AutoManager is classified under CMS in the PluginView directory.

How many fingerprint rules cover AutoManager?

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

What public signals suggest a site uses AutoManager?

Illustrative public indicators for AutoManager include .automanager.com/; link. A live scan may match additional proprietary rules beyond these examples.