PluginView

Detect Dealfront / Leadfeeder

Advertising, Attribution & Visitor Identification

PluginView detects Dealfront / Leadfeeder, a Advertising, Attribution & Visitor Identification, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Dealfront / Leadfeeder include sc.lfeeder.com/lftracker, lftracker.leadfeeder.com. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

01

Websites using Dealfront / Leadfeeder

Loading website list…

02

Signal classes

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

  • Vendor endpoints
03

Example public indicators for Dealfront / Leadfeeder

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

  • sc.lfeeder.com/lftracker
  • lftracker.leadfeeder.com
04

What a detection means

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.
05

Minimum proof rule

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

06

How to check a site for Dealfront / Leadfeeder

  1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Dealfront / Leadfeeder signals (prefer: B2B pages; observe visit).
  2. 2. PluginView reads only public responses (vendor endpoints) and scores them against the Dealfront / Leadfeeder signature set (2 rules).
  3. 3. Review the confidence score and text explanation for Dealfront / Leadfeeder on the results page.
07

FAQ: detecting Dealfront / Leadfeeder

Can PluginView detect Dealfront / Leadfeeder without logging in?
Yes. PluginView only reads publicly accessible responses when checking for Dealfront / Leadfeeder — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Dealfront / Leadfeeder?
Dealfront / Leadfeeder is classified under Advertising, Attribution & Visitor Identification in the PluginView directory.
How many fingerprint rules cover Dealfront / Leadfeeder?
This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Dealfront / Leadfeeder?
Illustrative public indicators for Dealfront / Leadfeeder include sc.lfeeder.com/lftracker; lftracker.leadfeeder.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Dealfront / Leadfeeder?
For Dealfront / Leadfeeder, start with: B2B pages; observe visit.