QR Code Analytics
A dynamic QR code routes every scan through a real redirect, which means every scan can be recorded. Here's exactly what that recording actually captures — no vague "gain insights" marketing, just the real fields.
What's recorded on every scan
- Total scans and unique visitors — a repeat scan from the same visitor on the same day is counted separately from a genuinely new visitor, so your totals aren't inflated by someone scanning the same code twice in a row.
- Country, region, and city — approximate geographic location for each scan, so you can see whether a code printed for one market is actually being scanned there.
- Device type — iOS, Android, Windows, macOS, or a general mobile/desktop split, so you know what you're actually designing a landing page for.
- Referrer — if the scan came through a link rather than a camera (for example, someone tapping a QR image embedded in a webpage), the referring page is recorded.
Comparing periods, not just totals
The per-code analytics view lets you switch between the last 7, 14, 30, or 90 days, and every number on the page — scans, unique visitors, top countries, device breakdown — updates to match the window you picked, with a comparison against the immediately preceding period of the same length. That means you can actually tell whether scans went up 40% because of something you did, or just because you're looking at a longer window than last time.
What this doesn't do — on purpose, stated plainly
This isn't a full marketing-attribution platform. There's no UTM-parameter capture and no conversion tracking built in yet — if someone scans your code and later buys something on your own site, this dashboard won't connect those two events for you. What it will tell you, reliably, is whether the code is being scanned at all, by roughly how many distinct people, from where, and on what kind of device. For a lot of real-world printed-material questions — "is anyone actually scanning this poster," "did the flyer at the trade show do anything" — that's the question that actually needs answering, and it's answered honestly here rather than papered over with a bigger-sounding claim.
Frequently asked questions
Do static QR codes show up in analytics?
No. A static code's data is read directly off the image by the scanning phone — no server is ever involved, so there's nothing to record. Only dynamic codes can be tracked, because tracking requires the scan to genuinely pass through a server first.
Is the location data exact, like GPS coordinates?
No, not by default — country/region/city is derived from the scanning device's IP address, which is approximate. Precise GPS coordinates are only ever captured on links that specifically use location-gated scanning, and only when the visitor's browser supplies them.
Does analytics tracking require a paid plan?
See the pricing page for exactly what's included at each tier.