Lead Generation
Lead Forensics
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Lead Forensics Ltd · www.leadforensics.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Lead Forensics is sold on B2B website visitor identification, and that is where the judges found substance: visitor identification scored 3-4, with company-level identification of visiting businesses, real-time alerts when a target business lands on the domain, alerts on key pages for up-sell and win-back, and automatic routing of opportunities to sales reps. CRM sync and export scored 2-3 on an automated one-way push of new leads to other platforms, though the platforms are not named. The criteria around that core tell the other story: data coverage sits at a flat 0, with no public record counts, DACH or EU coverage figures, verification methods or refresh cadence found; data provenance scored 1-2 with no public statement of data sources or legal basis; prospecting compliance scored 0-1 with no public suppression or do-not-contact handling; and sovereignty sits at a flat 1, with no sovereignty attributes on record and no public information on hosting or subprocessors. Judge scores varied by at most one point per criterion. A free trial and a revenue calculator are the only public commercial signals.
Speaks for it
- Company-level identification of website visitors is the documented core and scored 3-4.
- Real-time alerts when a target business lands on the domain, with automatic routing of opportunities to the right sales rep.
- Alerts on key account pages and engagement insights support up-sell, cross-sell and win-back.
- Integrations send new leads automatically to other platforms (CRM sync and export scored 2-3).
- A free trial and a revenue calculator are offered.
Held against it
- Data coverage scored a flat 0, with no public record counts, per-country coverage or verification and refresh detail found.
- Data provenance scored 1-2; we found no public information on where contact data comes from or the legal basis for EU records.
- Prospecting compliance scored 0-1; we found no public information on suppression, do-not-contact handling or lawful-outreach guidance.
- Sovereignty scored a flat 1, with no sovereignty attributes on record and no public information on hosting, contracting entity or subprocessors.
- Pricing transparency scored 0-1; a free trial and a revenue calculator are the only public commercial signals.
Best for
- You want real-time alerts when named target companies land on your website and automatic routing of opportunities to the right rep.
- Your account management team needs alerts on key customer pages to spot up-sell, cross-sell and win-back opportunities.
- You run an alert-driven workflow and only need a one-way automatic push of new leads into your existing platforms.
- You already have a target list and want per-account engagement insights rather than a prospecting database.
Avoid if
- You need documented coverage — record counts, DACH or EU figures, verification and refresh cadence — to hold the vendor to an accuracy standard.
- Your DPO requires a stated legal basis for EU records or a consent position for the tracking script before pointing it at EU traffic.
- You need suppression, do-not-contact handling or guidance on what you may lawfully do with identified contacts.
The scores
Coverage, accuracy & freshness
Show reasoningHide reasoning
How this is scored
How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.
0 — No stated coverage, no refresh cadence, no verification method; accuracy asserted as a percentage with nothing behind it.
3 — Headline record counts for the whole database, thin or unstated European coverage, and no description of how often records are re-verified.
5 — Coverage stated per country or region including DACH, email verification described, a stated refresh cadence, and firmographics beyond name and domain.
8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.
10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.
The SDR Team Lead
I found no public information on company or contact coverage — no record counts for DACH, the EU or anywhere else — and nothing on how records are verified or how often they are refreshed. A database I cannot size or trust at the record level is a connect-rate gamble, and the captured pages give me nothing to check. 1
The RevOps Manager
The captured pages describe visitor identification and account-management insights but we found no public information on database size, per-country coverage including DACH, verification methods or refresh cadence. There is nothing here to hold a vendor accountable on accuracy. 1
The Data Protection Officer
The captured pages position the product solely as a B2B website visitor identification tool; we found no public information on any database coverage by country or region, verification methods, or refresh cadence, and nothing at all for DACH or the wider EU. 1
The ABM Marketer
The captured pages describe a website visitor identification product, not a prospect database: no record counts, no DACH or EU coverage, and nothing on how records are verified or refreshed. I found no public information here on how much of any target market the data actually covers. 1
The DACH Sales Director
The page sells the promise — the self-styled "#1 B2B website visitor identification tool" — but I found no public information on how many companies the database resolves, coverage for Germany, Austria or Switzerland, or any verification and refresh cadence. For a Mittelstand pipeline, an accuracy story this empty is unscoreable from the outside. 1
The Skeptic
The captured homepage markets website visitor identification and nothing else: we found no public information on coverage by country or region, verification methods, or a refresh cadence, and not even an accuracy percentage to interrogate. 1
Data sources & lawful basis
Show reasoningHide reasoning
How this is scored
Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.
0 — No statement of where contact data comes from or on what legal basis; "GDPR-compliant" asserted without explanation, and no way for a listed person to object.
3 — Sources described in general terms ("public sources", "partners"), legitimate interest named without any balancing, and an opt-out request form as the only route for data subjects.
5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest stated as the basis for EU records, a dedicated privacy notice for the people in the database, and a self-service opt-out or removal process.
8 — The above plus an Art. 14 notification practice described (people informed when added), contributory or browser-extension collection disclosed as such, a legitimate-interest assessment summarised publicly, and EU records handled differently from US records where the law differs.
10 — Provenance is traceable per record: the source and collection date available for each contact, Art. 14 notices sent and documented, the balancing test published, objections honoured across the whole dataset and suppressed permanently, and no data sourced by scraping behind logins or from contributors' address books without their contacts' knowledge.
The SDR Team Lead
The captured pages describe visitor identification but give no statement of where the contact data comes from or on what legal basis it is processed. A privacy policy link and a 'Do not sell my data' option at least hint a listed person can act on their record, which keeps this just off the floor, but no legitimate-interest position or notice practice is evidenced. 1
The RevOps Manager
A privacy policy, cookie policy, trust center and a do-not-sell option are visible, which is more than nothing. But we found no public information on where contact data comes from, the legal basis for processing EU records, or a route for people in the database to object and be removed. 1
The Data Protection Officer
A privacy policy and a "do not sell my data" option exist, but that is a US-style selling opt-out, not a GDPR objection or removal route for the people in the database. We found no public information on where contact data originates, the legal basis for EU records, any balancing of legitimate interest, or any Art. 14 notice sent to identified individuals. 1
The ABM Marketer
A privacy policy, cookie policy and a do-not-sell option are linked, which at least gives listed people a route to object. Beyond that, we found no public information on where contact data comes from or on what legal basis it is processed. 1
The DACH Sales Director
The only data-subject-facing artifacts are a "Do not sell my data" option, a privacy policy and a trust center, which reads more Californian than European. I found no public information on source categories, whether legitimate interest is named as the basis for EU records, or a route for someone in the database to object and be removed. 1
The Skeptic
A privacy policy, cookie policy, trust centre and a "Do not sell my data" option are linked in the footer, which is more than nothing, but we found no public information on where contact data comes from, the legal basis relied on, or a route for a listed person to object and be removed. 1
Visitor identification & intent signals
Show reasoningHide reasoning
How this is scored
Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.
0 — No visitor identification or intent data, or person-level identification of EU visitors with no statement of legal basis.
3 — Reverse-IP company identification with a cookie-setting script, no statement about consent, and match rates claimed without method.
5 — Company-level identification with filters, visit history per company, a stated position that the script requires consent where it sets cookies, and a consent-mode or cookieless option.
8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms, intent topics or page-level signals with the source of third-party intent data named, and alerts routed to owners.
10 — Identification that survives a DPO review: no personal data of visitors stored, the TDDDG and GDPR position published and specific, third-party intent data sourced from a named co-op or panel with its consent basis stated, and scoring on intent that the user can trace back to the underlying visits.
The SDR Team Lead
Company-level identification is the documented core — the pages describe identifying which companies visit, real-time alerts when a target business lands, and engagement insights per account — and a cookie policy is linked. I found no public statement that the tracking script requires consent where it sets cookies, nor any consent-mode or cookieless option, so this sits at the reverse-IP tier my DPO would grill before we pointed it at German traffic. 1
The RevOps Manager
Company-level identification is the documented core, with real-time alerts on target businesses and key pages, routing to reps, and a first-party store of identified companies. We found no public position on consent where the script sets cookies, no cookieless or consent-mode option described, and no method behind the quality claims. 1
The Data Protection Officer
Company-level identification of website visitors is well evidenced, with real-time alerts when a target business lands on the domain, alerts on key pages, and automatic routing of opportunities to sales reps. We found no public information on whether the tracking script sets cookies, the vendor's position on consent under the German Telecommunications-Telemedia Data Protection Act, or any consent-dependent or cookieless mode of operation — only that a cookie policy is linked. 1
The ABM Marketer
Company-level identification is confirmed and the alerting is exactly what I need: real-time alerts when a target business lands on the domain, routed automatically to the right rep, with alerts on key account pages. But we found no public information on consent handling for the tracking script under the German telecom-data law, cookieless operation, or any named third-party intent source. 1
The DACH Sales Director
Company-level identification is explicit — it names "which companies visit your website" — with real-time alerts when a target business lands and automatic routing to the right rep, which is the right architecture. But I found no public information on a stated position on consent for the tracking script, a consent mode or a cookieless option, so I cannot tell a German DPO how it behaves for EU traffic without consent. 1
The Skeptic
Company-level identification is the core product with real-time alerts when a target business lands and per-account engagement insights, which is the right level of granularity; we found no public information on the consent position for the tracking script, a consent-mode or cookieless option, or how match rates are determined. 1
Prospecting workflow & outreach rules
Show reasoningHide reasoning
How this is scored
Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.
0 — A search box and an export button; nothing on the pages about what the buyer may lawfully do with the contacts.
3 — Filters on firmographics and job title, saved lists, and a terms clause making the customer solely responsible for compliance.
5 — Advanced filters including technographics and triggers, company-level lists and alerts, a global suppression or do-not-contact list, and guidance on cold outreach rules in the main EU markets.
8 — The above plus country-aware handling (for example flagging German contacts where cold calls and emails require consent), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.
10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.
The SDR Team Lead
The pages show real-time alerts on target businesses and automatic routing of opportunities to reps, but I found no public information on search filters, a suppression or do-not-contact list, or any guidance on what a buyer may lawfully do with the identified companies. Every UWG and GDPR question stays on my side of the table. 1
The RevOps Manager
The pages cover alerts and automatic routing but we found no public information on list-building controls, a suppression or do-not-contact list, or guidance on cold outreach rules in any market. Nothing addresses what a buyer may lawfully do with identified contacts, which leaves the legal risk entirely with the customer. 1
The Data Protection Officer
The pages describe spotting high-intent leads and routing them to reps, and we found no public information on search and list building, suppression or do-not-contact handling, do-not-call register checks, or any guidance on what the buyer may lawfully do with the identified contacts under German or other EU outreach rules. 1
The ABM Marketer
We found no public information on search filters, list building, suppression or do-not-contact handling, or any guidance on cold outreach rules in the main EU markets. Nothing on the captured pages tells me what I may lawfully do with identified accounts once I have them. 1
The DACH Sales Director
The workflow ends at spotting high-intent visitors and routing opportunities to reps; I found no public information on suppression or do-not-contact lists, checks against national do-not-call registers, or any guidance on cold outreach rules under UWG §7. The "Do not sell my data" option concerns the vendor's own data sales, not what a buyer may lawfully do with a lead. 1
The Skeptic
The page shows alerting and automatic routing of opportunities to sales reps, but we found no public information on search filters, saved lists, suppression or do-not-contact handling, or any guidance on what the buyer may lawfully do with identified contacts. 1
CRM sync, enrichment & export
Show reasoningHide reasoning
How this is scored
Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.
0 — Manual CSV export only; no CRM integration and no API.
3 — A one-way push to one CRM, CSV export, and no statement on whether exported data may be kept after cancellation.
5 — Native sync with the major CRMs including field mapping and deduplication, enrichment of existing CRM records, and a documented API with stated limits.
8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with credit costs per call published, and data retention rights after cancellation stated plainly.
10 — The vendor treats the buyer's CRM as the system of record: objections and corrections propagated into synced records automatically, full change history per field, a versioned API with a deprecation policy, and exit terms that say exactly which data the customer may keep and for how long.
The SDR Team Lead
Integrations are described as sending new leads straight to other platforms automatically — a one-way push, not a sync. I found no public information on field mapping, an API, or whether exported data may be kept after cancellation. 1
The RevOps Manager
Integrations are described as sending new leads straight to other platforms automatically — a one-way push, no more. We found no public information on field mapping, deduplication, re-enrichment of existing CRM records, API limits, or whether exported data may be kept after cancellation, which are the terms I need before letting a tool near my CRM. 1
The Data Protection Officer
Integrations that "send your new leads straight to your other platforms" evidence an automatic one-way push, though the supported platforms are not named. We found no public information on an API, field mapping, enrichment of existing records, or whether exported data may be kept when the subscription ends. 1
The ABM Marketer
"We'll send your new leads straight to your other platforms" evidences an automated one-way push into other systems, which suits an alert-driven workflow. We found no public information on field mapping, an API, or what happens to exported data and my access to it if the subscription ends. 1
The DACH Sales Director
Integrations are described as sending new leads "straight to your other platforms" automatically, which is a one-way push, though I found no public information naming the platforms, on field mapping, on a documented API, or on what a customer may keep after cancellation. That is a bare minimum for feeding a CRM. 1
The Skeptic
Integrations are described as sending new leads straight to other platforms automatically, a one-way push to unnamed systems; we found no public information on named CRM sync, field mapping, enrichment, an API, or what happens to exported data when the subscription ends. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and EU residents' contact data processed outside the EU with no stated transfer basis.
3 — Non-EU contracting entity with an EU representative under Art. 27, or EU hosting offered while enrichment, support or AI processing stay non-EU.
5 — EU contracting entity and EU hosting as standard, but parts of the chain — data partners, enrichment sources, tracking infrastructure — are non-EU without an explained safeguard.
8 — EU contracting entity and controller, EU hosting on named infrastructure, subprocessor and data-partner list published, and any non-EU transfer named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, controller, hosting, data partners and every subprocessor European, certification published, and a DPA covering both the customer's data and the database records the customer exports.
The SDR Team Lead
No sovereignty details are on record: the captured pages show UK and US support phone lines and I found no public information on where EU visitors' data is hosted, which entity contracts, or which subprocessors see it. A Trust Center link exists in the footer, but its contents are unevidenced, so this is close to the floor on a criterion that should decide the deal. 1
The RevOps Manager
The vendor is a UK company and we found no public information on hosting location, the contracting entity, subprocessors, data partners, or any transfer basis for EU residents' data. For a product built on identifying European website visitors, complete silence on every sovereignty attribute is disqualifying as it stands. 1
The Data Protection Officer
The vendor is a UK company advertising UK and US support lines, and no sovereignty attributes are on record: we found no public information on where hosting sits, who the contracting entity and controller are for EU customers, or which subprocessors and data partners see the data — only that a Trust Center is linked. 1
The ABM Marketer
The vendor is a UK entity with a stated US presence, and we found no public information on hosting location, the controller, or subprocessors for EU residents' data. Before putting my account data through this, I'd need those spelled out, and a trust center link alone doesn't do it. 1
The DACH Sales Director
The contracting entity is a UK company with UK and US support lines, and I found no public information on hosting location, subprocessors or data partners, or any stated transfer basis for EU residents' data. A privacy policy and trust center exist, but nothing published here shows EU-side hosting or European data handling. 1
The Skeptic
No sovereignty attributes are on record: we found no public information on hosting locations, the contracting and controller arrangements, or subprocessors, and the vendor presents as UK-based with a US presence — nothing captured speaks to where EU visitors' data sits or under what transfer basis. 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.
0 — No public prices at all; every tier is a sales conversation.
3 — A monthly headline exists, but what a credit buys, whether credits expire, or the cost of an additional seat is unstated — the invoice is unknowable.
5 — Tier prices public with credit allowances given, but at least one commonly needed piece (mobile numbers, extra seats, API access, CRM sync) is unpriced or behind a sales call.
8 — Every tier priced publicly with credits per data type, credit expiry and rollover, per-seat costs, overage rates, minimum term and VAT treatment stated.
10 — Complete price computability: the annual invoice derivable for a given number of seats, exported contacts by data type, identified companies and API calls, with every credit cost and the refund rule for inaccurate data published.
The SDR Team Lead
The only public offers are a free trial and a revenue-and-lead calculator; I found no public information on tier prices, credit costs, seat pricing, minimum terms or VAT treatment. The calculator estimates the revenue I am missing, not the invoice I would pay, so the real annual cost is a sales conversation. 1
The RevOps Manager
No public prices appear on the captured pages; the only commercial items are a free trial offer and a revenue calculator that estimates the buyer's missed leads rather than the product's cost. We found no public information on tier pricing, credits, seats or contract terms, so the invoice is not computable from public pages. 1
The Data Protection Officer
The only commercial offers on the captured pages are a free trial and a revenue calculator; we found no public information on tier prices, credit costs per data type, seat pricing, contract terms, or any other element of the real annual cost. 1
The ABM Marketer
The only commercial signals on the captured pages are a free trial and a revenue calculator; no tier prices, credit costs, seat pricing or contract terms appear anywhere. I cannot compute even a rough annual invoice from what is shown. 1
The DACH Sales Director
The only public commercial artifacts are a free trial and a revenue calculator that estimates missed leads; I found no public information on tier prices, credit costs, seat fees, minimum term or VAT treatment. A buyer cannot estimate the annual invoice from what is published. 1
The Skeptic
A free trial and a revenue calculator are offered, but we found no public information on tier prices, credit costs by data type, seat pricing or contract terms — the real annual cost cannot be computed from public pages. 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 8 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.leadforensics.com Checked 29 Sep 2026 Details →
- 2 Visitor identification & intent signals — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
- 3 Visitor identification & intent signals — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
- 4 Prospecting workflow & outreach rules — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
- 5 Prospecting workflow & outreach rules — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
- 6 CRM sync, enrichment & export — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →
- 7 CRM sync, enrichment & export — found from sitemap www.leadforensics.com Checked 1 Oct 2026 Details →