Lead Hub: One Record Per Person. Every Source, Together.

A customer who scans a QR lead-capture gate on Monday, fills out a landing page form on Wednesday, and shows up again in a CSV you import next month is still one person — not three disconnected rows. SMLLR's Lead Hub (Pro plan and above) deduplicates every captured contact by phone number or email address, merging every touchpoint into a single canonical record regardless of which source captured it.

Being in Lead Hub does not automatically mean a lead can be messaged. Every consent is captured for a specific purpose — email marketing or ad targeting today — as its own append-only, immutable record: the exact wording shown at the moment of opt-in, a timestamp, and the IP address, never edited or overwritten after the fact. A lead with no consent purposes granted still shows up in Lead Hub for attribution and reporting purposes, but cannot be messaged on any channel until they grant it. This purpose-specific model exists because consent to receive email is not the same thing as consent to be shown targeted ads, and treating them as one blanket "yes" doesn't hold up under DPDP's purpose-limitation principle.

Lead Hub itself requires a Pro plan or above — fitting, since every source that feeds it is Pro-and-above too. The QR Lead Capture Gate collects a phone number or email before or after a scan redirects. Landing page lead-capture forms (Pro plan and above, same as Custom Landing Pages) collect contact details directly on the page. CSV Import parses your spreadsheet in the browser in chunks, validates and normalizes each row, and reports invalid rows before anything is committed — so a handful of bad rows never blocks the rest of a large import.

Lead Hub is not a dead-end contact list — it is the audience source for Email Marketing. When you send a campaign, SMLLR pulls only the leads with an active email-marketing consent grant, and shows you exactly how many of your total leads currently qualify before you pick recipients. One record, one consent history, reused correctly across every channel that reads from it.

Leads are retained indefinitely while your account is active — there is no automatic expiry on a captured contact. Erasure is a deliberate, explicit action instead: an admin-triggered hard delete removes the lead record along with its touchpoints and consent history, for the cases where a data-subject erasure request needs to be honoured.