Home Dynamic QR Scan Analytics
Scan Analytics
Find out whether the print run worked, without a cookie or a pixel.
no subscription · pay per scan · nothing to cancel
The campaign works, and that is when the numbers stop
Print is the one channel where the honest answer to how did it do is often a shrug. Where measurement does exist, several platforms ration the view rather than the scanning.
- A static code touches no server, so nobody can tell you whether anyone scanned it.
- Total website traffic mixes every channel together and answers nothing about the flyer.
- Some platforms cap analytics visibility by tier, so the data stops exactly where the campaign starts succeeding.
- Adding a third-party tracker to the destination introduces a consent banner and a vendor.
What a scan leaves behind, and what it does not
The scan passes through the short URL
The redirect is the measurement point. This is also why static codes can never be counted: no request of theirs reaches anyone.
The request itself is recorded
Country, city, device, browser, OS, referrer and campaign source come from the request. Scanner-local hour comes from its timezone.
byCountry · byDevice · byOs · byReferrer · byUtmSource · byHourRepeat visitors without an identifier
New against returning is estimated with a probabilistic sketch rather than an identifier stored on the device. It is a count, not a profile.
What gets recorded, on every pack
- Where, at two resolutions
Country is the reliable tier. City is best-effort and useful in aggregate for deciding where the next batch goes.
- What it was scanned on
Device, browser and operating system, which is how you find out a campaign reached almost nobody on Android.
- When, in local time
Hour of day in the scanner own timezone, plus day-of-week against hour, so a lunchtime pattern is visible as one.
- Which channel
Referrer and campaign source, so a code that also lives in an email can be told apart from the printed one.
- Bots counted separately
Automated scans are flagged and shown rather than quietly folded into the total.
- No cookie, no pixel
Nothing is written to the scanning device and no third-party script is involved, so there is nothing to ask consent for on our side.
Questions
Can I get analytics for a static QR code?
No, and nor can anyone else. A static code carries its destination in the pattern, so the phone goes straight there and no request reaches a server that could count it.
Do you set a cookie or use a tracking pixel?
Neither. The record is made from the redirect request itself, first-party. Repeat behaviour is estimated with a probabilistic sketch rather than an identifier stored on the device.
How long is scan history kept?
Detailed windows run to 90 days live, and longer ranges are served from a nightly rollup. Some platforms keep per-scan detail longer than we do, so if multi-year forensic detail matters this is worth checking against your own requirement.
What does the unique visitor number actually count?
Distinct visitors per day, summed across the window you are looking at. Someone who scans on ten days counts ten times, which is why it is labelled as a daily sum rather than presented as the number of distinct people.
Does every scan cost a credit even if it is a bot?
A scan that resolves is 1 credit, and automated scans are flagged in the reporting so you can see what share of your traffic they are.