QR Code Analytics & Tracking Explained

What's actually measurable

• Scan count. The most reliable metric — a straightforward count of how many times the redirect URL was requested. This is a genuine, accurate count of scans, though it's worth noting a "scan" only means the redirect fired, not that the person did anything meaningful once they landed on the destination.
• Timestamp. When each scan occurred, which is useful for understanding patterns — a restaurant might see menu scans cluster around meal times, or a real estate sign might show a spike right after an open house is advertised.
• Approximate location. Derived from the scanning device's IP address, this gives a rough geographic read — typically city-level at best, sometimes less precise depending on the network the phone was connected to (a scan over cellular data vs. a public WiFi network can report differently). This is not GPS-precise location and shouldn't be treated as such.
• Device type and OS. Whether the scan came from iOS or Android, and sometimes browser type, pulled from the same request headers any web server logs.
• Referring code, if multiple codes point to the same destination. If you're running the same campaign across several different physical placements (different codes on different flyers, for instance), most platforms let you distinguish which specific code drove which scans — useful for comparing placement effectiveness.

What it can't tell you

Scan data is a proxy for interest, not a full picture of outcome. It generally can't tell you whether the person who scanned actually read the page, made a purchase, or took any action after landing — that requires separate tracking on the destination page itself (standard web analytics, conversion pixels, or a dedicated landing page with its own event tracking). It also can't reliably distinguish a genuine scan from a bot or crawler occasionally hitting the redirect URL, though this is a relatively minor source of noise for most real-world use cases compared to the scan count from actual users.

Using scan data well

The most useful application of scan analytics is usually comparative rather than absolute — not "we got 340 scans," but "the table tent version got three times the scans of the wall-mounted version," or "scans spiked the week we ran the direct mail piece." Comparing scan volume across placements, time periods, or campaign variants tells you far more than the raw number in isolation. If you need to understand what happens after the scan — actual conversions, time on page, follow-through — pair the QR code's redirect analytics with standard analytics on the destination page itself, rather than expecting the QR platform's scan count alone to answer that question.