LeadLab (WiredMinds)
How to configure LeadLab (WiredMinds) 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 LeadLab and how to reflect it in the Consenter Manager.
- Configure the third-party service.
- Map the configuration in the Consenter Manager.
- Update your privacy policy to reflect the actual implementation.
The configuration is a comparative example, not a guarantee of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.
At a glance
Scope. WiredMinds LeadLab B2B visitor identification via its JavaScript tracking code. WiredMinds GmbH is a German company.
What the service does in this scope. Before visitor behaviour is recorded, the IP address is compared against WiredMinds' company database (whitelist procedure) and deleted after the comparison; the IP address is not stored in LeadLab "under any circumstances". IP addresses not found in the whitelist are deleted immediately and the visit is anonymised; LeadLab does not carry out profiling. No cookies are created for tracking. WiredMinds names legitimate interest (Art. 6(1)(f) GDPR) as the basis and concludes a data processing agreement (AVV) with all customers. An opt-out link sets a cookie to exclude the browser.
Simplified format. LeadLab documents no alternative privacy settings beyond IP blacklists for internal traffic. The guide uses a single fixed-behaviour configuration.
⚠ Recommendation — running LeadLab before consent is legally uncertain. WiredMinds positions LeadLab as usable without consent. The script runs in the browser and the IP address is processed transiently. Have your DPO or independent counsel confirm before loading LeadLab without consent.
Step 1 — Configure LeadLab
| Configuration area | Fixed behaviour / required action |
|---|---|
| Processing purposes | Support marketing analytics; Receive marketing offers (if identified companies are approached) |
| Cookies | None for tracking |
| IP handling | Whitelist comparison, then deletion; never stored |
| IP blacklist | Configuration area: add internal IPs |
| Opt-out | wiredminds.optOut link in the privacy policy |
| Data processing agreement | AVV with WiredMinds |
| Loading | See ⚠ recommendation |
Step 2 — Map the configuration in the Consenter Manager
| Consenter Manager field | Value to select | Basis and conditions |
|---|---|---|
| Processing purposes | Support marketing analytics, Receive marketing offers | Company identification. |
| Tracking method | No tracking | No cookies. |
| Identifier | IP address | Processed transiently. |
| Data categories | IP address, Browsing and interaction data, Aggregated site statistics | Visitor behaviour of identified companies. |
| Legal role of data recipient | Processor | AVV. |
| Personalisation model | Group based (properties) | Company-level segmentation. |
| Maximum storage duration | Not documented | IP deleted after comparison. |
| Processing location | Germany | WiredMinds GmbH. |
Privacy-policy follow-up
- WiredMinds as processor; whitelist comparison and deletion of IP addresses; no cookies; opt-out link.
Verification checklist
- No LeadLab cookies set (except opt-out cookie on request).
- AVV concluded; opt-out link published.
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