Detect Ackee

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

• JavaScript globals
• DOM selectors

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

• ackeeTracker

Establishes

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

Does not establish

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

Can PluginView detect Ackee without logging in?

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

What category is Ackee?

Ackee is classified under Analytics in the PluginView directory.

How many fingerprint rules cover Ackee?

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

Illustrative public indicators for Ackee include ackeeTracker. A live scan may match additional proprietary rules beyond these examples.