Blog
How to track QR code scans (and what the data actually tells you)
How to track QR code scans starts with one requirement: the code must go through a measurable redirect. Static patterns that encode a raw URL never report back to you. Dynamic QR codes on Qristic log scans when people open the short link.
Scan data is useful — and easy to misread. This post covers what the numbers actually tell you, and what they do not.
Why static codes cannot be tracked
A static QR that opens https://example.com sends the phone straight to that site. Your QR tool never sees the scan. If you need analytics, you need a dynamic (or otherwise instrumented) hop.
What scan counts usually mean
A scan event typically means “someone opened the short link.” It does not always equal a unique person, a purchase, or even a successful read of your offer. Phones may prefetch, staff may test codes, and one guest may scan twice.
Treat scans as a directional signal for placement and creative tests: did the patio tent outperform the register card this week?
What the data does not tell you (alone)
- Conversion quality — pair with on-site analytics or POS data
- Exact demographics — cameras are not identity providers
- Whether the print is scannable everywhere — still test substrates
Practical tracking workflow on Qristic
Create a dynamic QR, print it, and review scan activity in your dashboard. Use one code per placement when you want clean comparisons. For menus and campaigns, see the dynamic product page; for product units, claimable activation is a different measurement story.
FAQ
Do I need a QR Pack to track scans?
Scan tracking is tied to Dynamic QR workflows, which use Dynamic credits from a QR Pack. Static free codes do not report scans.
Can I track a Wi‑Fi QR?
Raw Wi‑Fi payload codes are usually static and untracked. Track a welcome-page URL with a dynamic code if you need counts.
Related
Dynamic QR & scan tracking · Dynamic vs static · QR code for menus · All blog posts