Source-Attribution Reporting: Which QR Code Actually Produced This Lead

A QR code's scan count tells you how many people pointed a camera at it — it doesn't tell you how many of those scans turned into an actual lead. A billboard code and a counter-card code can both show 500 scans this month and still be performing completely differently, if one converts 40 of those scans into captured contacts and the other converts four. Source-attribution reporting is the practice of tracing every lead back to the exact placement that produced it, so a business running QR codes across multiple print locations, packaging runs, or events can tell which ones are actually working, not just which ones are getting looked at.

Every time SMLLR's Lead Capture Gate converts a scan into a lead, it records a touchpoint that snapshots the source QR code's name, the campaign it belongs to (if grouped under one), and the scan's own city, device, browser, and OS — captured as it existed at that exact moment, not looked up live from the QR code's current settings. This matters for accuracy over time: if you later rename or redesign a QR code, or even delete it entirely, the historical attribution trail for leads it already produced stays intact and accurate, since it was frozen at the point of capture rather than dependent on the source record still existing.

Opening any individual QR code's own detail view shows a filtered lead list scoped to just that code — the direct answer to "how many leads has this specific billboard, table tent, or packaging SKU actually produced." Compare that count against the code's own scan total (visible in the standard reporting view) to get a genuine conversion rate per placement, rather than relying on scan volume as a stand-in for performance. A code with high scans and low leads is worth a second look at its gate's title or the value behind it; a code with modest scans but strong conversion may be worth replicating in more locations rather than assumed to be underperforming just because its raw scan number looks small next to a busier placement.

A single print run, packaging refresh, or event often involves dozens of individual QR codes rather than one. Group the codes that belong to the same coordinated push under Campaign Manager, and their scan totals and lead counts roll up into a single combined number for that campaign — a "Diwali Packaging 2026" campaign shows one lead count regardless of how many individual SKU-level codes fed it, while each individual code underneath it still keeps its own attribution for a closer look when you need it.

Because SMLLR's dynamic QR codes can have their destination changed without reprinting, the same physical code can sit on a location or asset across multiple campaigns over time. Each touchpoint's snapshot preserves which campaign was active at the moment of that specific capture, so switching a code's target URL or campaign assignment for a new push doesn't retroactively reassign or blur the attribution of leads it already captured under the previous one.

A chain running the same lead-gated QR code design across ten outlets — printed as ten physically distinct codes, one per location — can compare lead counts location by location rather than reading one blended account-wide number. That's the difference between knowing "we got 400 leads this month" and knowing "our MG Road outlet's counter card converted three times better than our Whitefield outlet's," which is the number that actually tells you where to reprint, where to redesign, or where to invest in a better-placed code.