Detect LeadScore

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

• JavaScript globals

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

• trackLeadScore

Establishes

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

Does not establish

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

Can PluginView detect LeadScore without logging in?

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

What category is LeadScore?

LeadScore is classified under Marketing automation in the PluginView directory.

How many fingerprint rules cover LeadScore?

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

What public signals suggest a site uses LeadScore?

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