Set up your bannerConfigure Your ToolsB2B Visitor Identification

Lead Forensics

How to configure Lead Forensics 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 Lead Forensics 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 Lead Forensics tracking code for reverse business-IP identification.

What the service does in this scope. The JavaScript collects non-personal attributes and the IP address and matches business IP addresses to organisations. The basic code does not drop a cookie; the optional advanced code sets the lfuuid cookie (a random GUID) to improve match rates and "should be placed behind a consent banner". Lead Forensics acts as data processor under a DPA. Data may be processed by group companies including Lead Forensics Limited (UK) and Lead Forensics, Inc. (US).

Configurations included.

ConfigurationSummary
Configuration A — Medium risk (⚠ no-consent)Basic code only (no cookie).
Configuration B — Higher riskAdvanced code with lfuuid cookie, after consent.

⚠ Recommendation — running the basic code before consent is legally uncertain. Lead Forensics requires consent only for the advanced (cookie) code. The basic script still runs in the browser and processes the IP address. Have your DPO or independent counsel confirm before loading it without consent.

Step 1 — Configure Lead Forensics

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionSupport marketing analytics; Receive marketing offersSame
2Code versionLead Forensics portal: basic vs. advanced codeBasicAdvanced
3LoadingConsenter script blockingSee ⚠ recommendationAfter consent
4Contact data featurePortal featureNot usedOptional (add "direct identifier")
5DPALead Forensics DPAConcludedConcluded

Step 2 — Map the configuration in the Consenter Manager

Processing location. Group processing includes Lead Forensics, Inc. in the US, subject to the US CLOUD Act.

Consenter Manager fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesSupport marketing analytics, Receive marketing offersSupport marketing analytics, Receive marketing offers
Tracking methodNo trackingFirst party tracking (cross-session)
IdentifierIP addressDevice identifiers, IP address
Data categoriesIP address, Browsing and interaction data, Device characteristicsIP address, Device identifiers, Browsing and interaction data, Device characteristics
Legal role of data recipientProcessorProcessor
Personalisation modelGroup based (properties)Group based (properties)
Maximum storage durationNot documentedNot documented
Processing locationUK; United StatesUK; United States

Privacy-policy follow-up

  • Lead Forensics as processor; business IP identification; cookie (B); group transfers to the US.

Verification checklist

  • A: no lfuuid cookie.
  • B: advanced code only after consent.

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