A QR code is a picture of a URL. That is the whole technology. Everything you can measure about a scan is what you could measure about a click on that URL, because that is what a scan is.
Once that lands, most QR questions answer themselves.
What a scan tells you
That it happened, and when. Timing is often the most useful part — a spike after a mailing lands, a pattern by day of week.
Rough location. Country reliably, region approximately. Enough to know a regional campaign reached its region.
Device type. Which matters, because it decides where the scanner should be sent.
Which placement, but only if you set that up in advance.
What it does not tell you
Not identity. Not demographics. Not whether the same person scanned twice.
A scan is an anonymous web request. Vendors implying richer data are either estimating or collecting something they should not be.
The mistake that cannot be undone
Encoding a store URL directly into a printed code.
Print is permanent. If the code goes straight to an App Store page, then Android scanners hit a dead end, you can never re-point it, and if the listing URL changes every printed copy dies.
Encode a link you control. The image stays identical; the destination is yours to change.
Telling placements apart
If a poster, a package insert and a trade show banner all encode the same URL, your report has one row forever. You will never know which one worked.
Give each its own link or its own campaign tag. It costs nothing at design time and is impossible to add later.
One measurement quirk worth knowing
If your system records a scan as both a scan and a click, your click total already includes scans. That is a reasonable design — a scan *is* a click — but it means adding the two double-counts.
Worth checking how your own tooling does it before reporting a number to anyone.
Frequently asked questions
- Can you track QR code scans?
- You track the URL the code encodes, not the code itself. A QR code has no reporting of its own — it is a picture of a link. Whatever analytics that link supports is what you get.
- How do I tell two printed placements apart?
- Give each placement its own URL or its own campaign parameter. A poster and a package that encode the same URL are indistinguishable in reporting forever, and print cannot be changed after the fact.
- What is a dynamic QR code?
- One that encodes a link you control rather than the final destination. The image never changes, but you can re-point where it goes. A static code that encodes a store URL directly can never be changed once printed.
- Can I see who scanned a QR code?
- No. You see what any web request shows: rough location, device type, and timing. Not identity. Anyone promising more than that is either guessing or collecting something they should not.
Read more
QR codes · 4 min read
QR codes for app downloads: what actually works in the wild
QR codes fail for boring, physical reasons — size, contrast, placement, and dead destinations. Here's what to get right so scans turn into installs, and why a static store link on a poster is a mistake.
Fundamentals · 1 min read
Bitly vs Dub vs Bridgly: picking by job
Bitly shortens. Dub pays digital partners. Bridgly routes app installs and ties physical QR scans to attributed sales and commissions.
Growth · 2 min read
Web to app: moving mobile web visitors into your app
Most mobile visitors land on your website, not your app. The handoff between the two is where installs are won or lost. Here is what works, what annoys people, and how to measure it honestly.