What Your QR Code Analytics Are Actually Telling You
Most people look at their QR code analytics, see a total scan count, and stop there. That number tells you almost nothing on its own. The useful information is in the detail — the patterns, the outliers, the gaps.
Here's how to read the data properly.
Total scans vs unique scans
Total scans counts every scan event. Unique scans filters out multiple scans from the same device within a time window.
Why it matters: if you have 200 total scans and 180 unique scans, your QR code is being scanned mostly by different people — broad reach. If you have 200 total scans and 40 unique scans, a small group of people are scanning repeatedly — possibly staff, possibly people having trouble with the destination, possibly a narrow but engaged audience.
Neither is inherently good or bad. But they tell you very different things about who's interacting with the code.
Scan volume over time
The time-series chart is where campaign insights live. You're looking for:
- Spikes that correlate with campaign activities — did the print drop drive scans?
- Decay curves — how quickly does scan volume drop off after a campaign ends?
- Sustained baseline — if you're still getting scans weeks after a campaign, something is working well
- Gaps — no scans for a week might mean the code is in a location it's not being seen
If you ran a flyer drop on the 3rd and your analytics show a spike on the 4th–6th followed by a clean decay, that's good data. It shows the flyer drove behaviour. If there's no spike, either the flyer didn't reach people, the call to action wasn't compelling, or the QR code had a design problem.
Geographic data
Where scans are happening tells you which physical locations, regions, or markets are responding. For campaigns running across multiple cities, geographic data tells you where to put more resource. For a business with multiple locations, it tells you which sites have customers actually engaging with QR codes.
Unexpected geographic data is often the most interesting. If you ran a national campaign but 80% of scans came from one city, something is working there that isn't working elsewhere. Find out what.
Device breakdown: iOS vs Android
Mostly useful for landing page optimisation. If 70% of your scans come from iOS and your landing page has a rendering issue on Safari, you have a problem that's affecting the majority of your audience.
Device data also informs deep link strategy. If you're linking to an app, knowing the OS split tells you whether you need to optimise the iOS or Android app store flow more urgently.
Scan time distribution
When are people scanning? Morning, lunch, evening? During business hours or outside them?
For restaurants, scan time tells you when the menu is being browsed most — before service, during, or people researching from home. For events, it tells you whether people are engaging in advance or on the day. For retail, it shows when products are being used.
What to do when scan rates are lower than expected
- Check the code is scanning correctly — test it yourself
- Check the destination is loading and is the right page
- Evaluate the placement — is the code visible and reachable?
- Evaluate the call to action — does it clearly say what happens on scan?
- Check the size — is it large enough for the expected scanning distance?
Low scan rates are usually a design or placement problem, not a 'QR codes don't work' problem. The data tells you there's an issue. Investigation tells you what it is.