Detect Lead Forensics

Establishes

The listed vendor-controlled browser component was present and active on the scanned page at scan time.

Does not establish

It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: B2B pages; observe visit

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Lead Forensics signals (prefer: B2B pages; observe visit).
2. 2. PluginView reads only public responses and scores them against proprietary Lead Forensics fingerprints. Rule bodies and identifiers are not published.
3. 3. Review the confidence score and text explanation for Lead Forensics on the results page.

Can PluginView detect Lead Forensics without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Lead Forensics. It does not bypass authentication or paywalls.

What category is Lead Forensics?

Lead Forensics is classified under Analytics, Advertising, Attribution & Visitor Identification in the PluginView directory.

Does PluginView publish Lead Forensics fingerprint rules?

No. Detection uses proprietary fingerprint rules that are not published. Scan results explain matches in plain language without disclosing rule bodies or identifiers.

Which pages are best for detecting Lead Forensics?

For Lead Forensics, start with: B2B pages; observe visit.