Detect LEADIN

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

• Script sources

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

• js.leadin.com

Establishes

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

Does not establish

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

Can PluginView detect LEADIN without logging in?

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

What category is LEADIN?

LEADIN is classified under Analytics in the PluginView directory.

How many fingerprint rules cover LEADIN?

This reference currently tracks 1 fingerprint rule across script sources. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses LEADIN?

Illustrative public indicators for LEADIN include js.leadin.com. A live scan may match additional proprietary rules beyond these examples.