Set up your bannerConfigure Your ToolsB2B Visitor Identification

Leadfeeder (Dealfront)

How to configure Leadfeeder (Dealfront) at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Support marketing analytics, Receive marketing offers

Overview

This guide explains how to implement different privacy configurations for the Leadfeeder Tracker and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. The Leadfeeder Tracker (Dealfront) for B2B company identification on a website.

What the service does in this scope. The tracker analyses technical signals such as the IP address, matches them against company databases and enriches the visit with firmographic details; the script is served via AWS CloudFront. It can set the _lfa cookie (1 year) as a visitor ID. With consent-manager support, the tracker sets cookies only after the CMP calls window.ldfdr.acceptCookie; until then, no cookie is dropped. IP anonymisation stores only a shortened IP address and keeps the actual IP out of all systems including logs. Dealfront states that it processes website traffic data on its own legitimate interest (Art. 6(1)(f) GDPR) in optimising its products, services, sales and marketing.

Configurations included.

ConfigurationSummary
Configuration A — Medium risk (⚠ no-consent)Cookieless company identification; IP anonymisation on; cookie only after consent.
Configuration B — Higher riskTracker with _lfa visitor cookie after consent; IP anonymisation off; CRM integration.

⚠ Recommendation — running the tracker before consent is legally uncertain. Dealfront positions company-level identification on legitimate interest. The script still runs in the visitor's browser and processes the IP address, which can be personal data; Dealfront itself notes that a balancing test is needed. Have your DPO or independent counsel confirm before loading the tracker without consent.

Step 1 — Configure Leadfeeder

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analyticsSupport marketing analytics; Receive marketing offers
2Cookie consent integrationTracker settings: consent-manager support; CMP calls window.ldfdr.acceptCookieCookie only after consentCookie only after consent
3IP anonymisationTracker settingsOnOff
4Tracker loadingConsenter / tag managerSee ⚠ recommendationAfter consent
5CRM integrationsDealfront integrations (e.g. HubSpot, Salesforce, Pipedrive)Not usedUsed

Step 2 — Map the configuration in the Consenter Manager

Processing location. Dealfront is an EU group; the script is delivered via AWS CloudFront. Amazon Web Services is a US enterprise subject to the US CLOUD Act; list the United States as a potential access location.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesSupport marketing analyticsSupport marketing analytics, Receive marketing offers
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierIP addressDevice identifiers, IP address
Data categoriesIP address anonymised, Browsing and interaction data, Device characteristicsIP address, Device identifiers, Browsing and interaction data, Device characteristics, Users' profiles
Legal role of data recipientProcessor; Dealfront also Individual Controller for its own product purposesSame
Personalisation modelNo personalisationGroup based (properties)
Maximum storage durationNot documented_lfa 1 year
Processing locationEU; United States as potential access locationSame

Privacy-policy follow-up

  • Dealfront (Leadfeeder) as recipient and, for its own purposes, controller; IP-based company identification; cookies (B); opt-out; transfers.

Verification checklist

  • A: no _lfa cookie before consent.
  • IP anonymisation setting matches the mapping.

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page