Detect Apptus

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

• Cookies
• Script sources
• JavaScript globals

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

• apptus.customerKey
• apptus.sessionKey
• cdn.esales.apptus.com.apptus-esales-api-.min.js
• ApptusEsales
• apptusConfig
• apptusDebug

Establishes

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

Does not establish

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

Can PluginView detect Apptus without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Apptus — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Apptus?

Apptus is classified under Personalisation in the PluginView directory.

How many fingerprint rules cover Apptus?

This reference currently tracks 6 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Apptus?

Illustrative public indicators for Apptus include apptus.customerKey; apptus.sessionKey; cdn.esales.apptus.com.apptus-esales-api-.min.js. A live scan may match additional proprietary rules beyond these examples.