Centralizing Leads From Print, Packaging & Events in One Dashboard

A business running QR codes across packaging, a print ad, and a trade show booth usually ends up with three different answers to "how many leads did we get this quarter" — one number from whoever manages the packaging QR, another from the print campaign's tracking sheet, and a third from whatever the events team scribbled down at the booth. None of those three lists know about each other, so the same person who scanned the packaging code and later filled out the booth's sign-up sheet shows up twice, counted as two leads instead of one warmer, more engaged one. SMLLR's Lead Hub exists specifically to collapse that into a single account-wide view, regardless of which source — or how many sources — actually captured any given contact.

Whether a contact comes from a QR code's Lead Capture Gate, a landing page's lead form, a CSV import of an existing list, or Play & Win's optional lead-gate step, it lands in the same Lead Hub table, deduplicated on the normalized phone number or email address. A person captured through a packaging QR code on Monday and again through an event landing page on Thursday is one lead with two touchpoints on their record, not two separate rows competing for the same follow-up call. Each lead's sourceTypes field lists every distinct channel that's ever captured them, so you can immediately see who's a single-touch lead and who's engaged across more than one campaign.

A packaging run alone might involve dozens of individual QR codes — one per SKU or per print batch — each capable of gating leads on its own. Left as individual codes, that's dozens of separate lead counts to reconcile by hand. Grouping the QR codes that belong to the same underlying push under Campaign Manager rolls their scan totals and lead counts up into one number instead, so a "Q3 Packaging Refresh" campaign shows a single combined lead count regardless of how many individual product codes fed it. The same grouping works across formats — a campaign can mix packaging QR codes, a print-ad QR code, and an event-booth QR code under one umbrella if they're genuinely one coordinated push.

Leads Hub's overview presents four live counts — Total Leads, New (7 Days), Marketing-Reachable, and No Consent Yet — plus a breakdown of how many leads came from the QR gate versus landing pages versus CSV import versus Play & Win, computed across the whole account regardless of source. From there, filtering down to a specific QR code's own detail view shows only the leads that code personally captured, useful when you need to know how one packaging SKU or one event booth performed in isolation rather than the account-wide total.

Different sources often know different things about the same person — a packaging QR gate might only ever capture a phone number, while a CSV import of your existing customer list might already have that same person's email and full name on file. When these merge into one lead, missing fields are backfilled from whichever source has them rather than one source's data silently overwriting another's — a name captured via CSV import stays on the record even after that same contact later scans a bare packaging code that only ever asks for a phone number.

The value of a unified dashboard compounds with every new source you add, not just print. A retail chain running packaging QR codes, in-store lead gates, and a periodic events calendar sees the real overlap between those channels — the customer who scans a code in-store and later meets your team at a trade show is the same warm lead twice, not two separate cold ones — and that overlap is invisible unless every source writes into the same place from the start. Starting with Lead Hub before adding a second or third capture channel avoids the retroactive cleanup of merging three separate spreadsheets after the fact.