Analytics
QR code analytics
Understand QR scan analytics, privacy limits, unique scans, devices, geography, campaigns, and exports.
QR code analytics show which codes and campaigns are scanned, when scans happen, where scans roughly come from, and which devices people use. Cue measures those answers without storing raw IP addresses in scan analytics.
Reviewed 2026-07-10
What QR analytics should answer
The useful questions are practical: which placement worked, when people scanned, whether scans were unique, what device class they used, and whether a campaign or A/B variant outperformed another.
What Cue records
Cue records minimal scan events for dynamic codes: salted visitor hashes, coarse geography, parsed device details, referrer, timestamp, and the code or campaign scanned.
What to avoid
Avoid QR analytics systems that turn scan measurement into person-level surveillance. Most marketing teams need placement and campaign performance, not invasive profiles.
Quick comparison
| Metric | Use it for | Cue approach |
|---|---|---|
| Scans | Campaign volume | Tracked per dynamic code and campaign. |
| Unique visitors | Deduplicated reach | Computed from salted visitor hashes. |
| Country/city | Regional performance | Coarse geography, not raw IP storage. |
| Device | Destination fit | Parsed category, OS, and browser family. |
Decision rules
- Use analytics to compare placements and campaigns, not to identify individual scanners.
- Check whether a vendor stores raw IP addresses and raw user agents.
- Make sure exports and dashboards match the retention period your team needs.
Frequently asked questions
Can static QR codes have analytics?
Not directly. A static code does not call Cue on scan, so there is no scan event to record. Use a dynamic code when analytics matter.
Does Cue store raw IP addresses for scan analytics?
Cue's public privacy and security pages state that scan analytics are designed around no raw IP storage, salted hashes, and coarse geography.