Lead Segmentation for QR-Sourced Leads

This is a guide to the real, practical ways SMLLR lets you slice a growing Lead Hub — by source, by consent status, and by the QR code or campaign that captured them. It's deliberately not about assigning a numeric "lead score" to rank contacts by how likely they are to convert — SMLLR doesn't compute one, and a QR-captured lead's context (a phone number from a packaging scan versus a full contact from an event landing page) is usually a better signal on its own than a synthetic score would be. What follows is what you can actually filter and act on today.

Every lead carries a sourceTypes tag listing every distinct channel that's captured them — QR lead capture gate, landing page form, CSV import, and Play & Win — and Leads Hub's source breakdown shows the account-wide split across all four at a glance. This is the first useful segmentation for most accounts: a lead captured only through a low-commitment QR gate scan is a different kind of contact than one who filled out a full landing-page form with a name and a specific message, even before you know anything else about them.

The Marketing-Reachable and No Consent Yet stat tiles are a live segmentation by consent — the single most actionable split for anyone about to run a campaign, since it's the difference between leads you can legally include in a send and leads you currently can't. Within "reachable," consent is further split by purpose: a lead with email-marketing consent but no ad-targeting consent is eligible for an Email Marketing send but won't appear in a Meta Sync audience, and vice versa. Checking this split before building a campaign audience avoids the false assumption that your total lead count and your usable audience are the same number.

Every QR code's own detail view shows a lead list scoped to just that code, and grouping related codes under Campaign Manager rolls that up to a campaign-level segment — the practical way an agency or multi-location business separates "leads from Client A's packaging run" from "leads from Client B's event booth" inside the same account, or separates one outlet's performance from another's within a single chain.

The New (7 Days) count on the Leads Hub overview is a rolling recency segment — the fastest-moving contacts worth a fresh follow-up before they go cold, as distinct from your full historical list. For a business running an ongoing packaging or in-store QR presence, checking this weekly is a lighter habit than re-reviewing the entire Lead Hub table for what's actually new.

A practical agency workflow looks like this: filter to one client's campaign (source + Campaign Manager grouping), narrow to leads with active email-marketing consent (consent segment), and check the New (7 Days) count separately to decide whether a welcome sequence or a general newsletter fits better. None of this requires exporting to a spreadsheet to cross-reference manually — every one of these segments is visible natively inside Leads Hub or surfaced automatically when you go to build a send in Email Marketing or a sync in Meta Sync.