Does Leadfeeder require consent?

Yes. Leadfeeder sets the persistent _lfa cookie and performs IP-based company identification, constituting personal data processing for marketing profiling. GDPR and the ePrivacy Directive require explicit consent before the tracker loads.

What does Leadfeeder collect from website visitors?

Leadfeeder captures visitor IP addresses for company identification, records page views and visit sequences, and stores results alongside firmographic enrichment data in connected CRM systems such as Salesforce and HubSpot.

How does ConsentStack block Leadfeeder?

ConsentStack blocks Leadfeeder until the visitor grants analytics and marketing consent. This prevents IP-based company identification and behavioral tracking from running on visitors who have not opted in, reducing regulatory exposure.

What tracker domains does Leadfeeder use?

ConsentStack has catalogued tracker domains for Leadfeeder including leadfeeder.com. These are the network destinations Leadfeeder's scripts contact, which a consent platform blocks until a visitor agrees.

Leadfeeder - B2B Visitor Tracking & Consent

Back to Vendor Library

Overview

Leadfeeder (now part of Dealfront) is a B2B website visitor identification platform that reveals which companies are visiting a website by matching visitor IP addresses against a database of corporate IP ranges. The platform turns anonymous website traffic into actionable sales leads by identifying visiting organizations, showing which pages they viewed, and scoring their buying intent. Leadfeeder is widely deployed by B2B sales and marketing teams to feed account-based marketing programs and outbound prospecting workflows.

What This Script Does

Leadfeeder deploys a tracking script on B2B websites to identify anonymous company visitors and capture behavioral signals.

Scripts loaded: The Leadfeeder tracker script loads from t.leadfeeder.com, initializing visitor identification and behavioral tracking
Reverse IP identification: On each page view, the script captures the visitor's IP address and matches it against Leadfeeder's (Dealfront's) database of company IP ranges, identifying the visiting organization without individual identification.
Behavioral tracking: The script records page views, visit duration, page sequences, and content engagement. This data builds intent scores and visit quality metrics for each identified company.
Cookies set:
- _lfa — First-party cookie. Leadfeeder's persistent visitor identifier linking page views across sessions for the same browser.
- _lfa_test_cookie_stored — First-party cookie. Tests cookie storage availability.
Data collected: IP address (for company identification), page URLs, visit timestamps, referrer, browser and device metadata, and session duration. Identified companies are enriched with firmographic data (industry, size, location).
CRM integration: Identified company visits are pushed to CRM systems (Salesforce, HubSpot, Pipedrive) and sales engagement tools for follow-up by sales teams.

Consent & Compliance

Leadfeeder falls under both analytics and marketing consent categories.

Under GDPR and ePrivacy, Leadfeeder's tracking requires explicit consent. The _lfa cookie is a persistent identifier, and the IP-based company identification processes personal data for profiling under GDPR. Dealfront (Leadfeeder's parent) is headquartered in Helsinki, Finland, and has addressed GDPR compliance with configurable consent modes. The ePrivacy Directive requires consent for the non-essential tracking cookies.

Under CCPA/CPRA, IP-based identification, behavioral tracking, and sharing of visit data with CRM systems constitute processing of personal information for marketing purposes.

Should You Block This Without Consent?

Yes. Leadfeeder sets persistent tracking cookies, performs IP-based company identification, and transmits behavioral data for sales and marketing purposes. Block the tracker until the user grants consent for analytics and marketing.

Is Leadfeeder GDPR compliant?

Leadfeeder typically loads analytics and marketing trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Leadfeeder can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Leadfeeder, not on Leadfeeder itself.

Visit website