Detect Amplience

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

• JavaScript globals
• DOM selectors

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

• amplianceTemplates
• link, img

Establishes

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

Does not establish

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

Can PluginView detect Amplience without logging in?

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

What category is Amplience?

Amplience is classified under CMS in the PluginView directory.

How many fingerprint rules cover Amplience?

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 Amplience?

Illustrative public indicators for Amplience include amplianceTemplates; link, img. A live scan may match additional proprietary rules beyond these examples.