You can track QR code scans, but only with dynamic QR codes. Dynamic codes route through a redirect service that logs every scan (time, location, device). Static codes skip the redirect, so there's nothing to track.
Can you track a QR code after printing it?
Only if it's dynamic. A dynamic QR code points to a short redirect URL instead of your destination directly. When someone scans it, the redirect server logs the scan before forwarding them to the real page. That log is your analytics.
A static code bakes the destination URL straight into the dot pattern. The scanner reads it and goes there, with nothing in between to log.
Static codes work forever without any infrastructure. Dynamic codes need a running redirect service, but they give you scan data and let you change where the code points after printing.
What gets logged on each scan: count, timestamp, approximate location (from the IP address), device and OS, browser or QR reader app.
What does the scan data actually tell you?
Collecting numbers is the easy part.
Scan volume over time tells you whether a campaign is working. A code on a conference badge that pulls 3 scans in two days and a code on a restaurant table pulling 40 per week are different stories. The trend matters more than the total, and a spike the day after a mailer drops is confirmation the channel pulled its weight.
Location data can surprise you. A US company running QR codes on packaging might see 30% of scans coming from Germany, a distribution signal that Google Analytics on the website would never surface.
If your device breakdown skews unusually toward desktop (normal is about 90/10 mobile), your code is probably on a webpage somewhere. People right-click and open the link instead of scanning.
Restaurant codes peak at lunch and dinner, event codes spike the morning of, retail codes scan most on weekends. When you see those patterns in your own data, you know when to rotate destinations or launch promotions behind your dynamic code.
Scan-through rates vary dramatically by context. Uniqode's platform analytics (April 2024) show the range across industries:
| Placement | Scan-through rate |
|---|---|
| Restaurants (menus, table cards) | 45.2% |
| Events and services | 18.1% |
| Food and beverage packaging | 14.9% |
| Consumer goods | 12.2% |
| Retail | 5.8% |
| Real estate | 4.8% |
Restaurant codes outperform everything else by a wide margin. Someone sitting at a table already wants something (the menu, the wifi, the bill), and the code is right in front of them.
How to get more scans
A QR code with no context is one people walk past.
Put a call to action next to the code. "Scan for the menu." "See your receipt." "Get 10% off." According to IMQRScan's platform analytics, adding a descriptive CTA lifts scan rates by roughly 37%. People need a reason to pull out their phone, and a naked QR code doesn't give them one.
Size and placement work in predictable ways. A 2cm code buried in a footer won't get scanned. The print rule of thumb is 10:1. A code scanned from 1 meter away needs to be at least 10cm wide. Eye level beats ankle level. Dedicated space beats afterthought.
Codes with custom colors and logos outperform plain black-and-white squares by about 29%, per IMQRScan. A code that looks like part of the design reads differently from a generic grid someone clearly pasted in at deadline.
QR code tracking vs UTM parameters
UTMs and QR code tracking answer different questions, and you should probably use both.
UTMs (?utm_source=flyer&utm_medium=print&utm_campaign=summer) tag the destination URL so Google Analytics can attribute the visit. They cover what happened after the click: pages viewed, time on site, conversions. QR tracking covers what happened at the scan: count, time, device, location. One scan produces one redirect; UTMs pick up the session from there.
Put UTM parameters in your dynamic code's destination URL and you get both layers of data. Scan-level detail from your QR platform, session-level behavior from Google Analytics.
Privacy and QR code tracking
Scan tracking collects metadata, not identity. An IP address, a device type, a timestamp. No cookies are set during the redirect. No login is required to scan.
IP addresses qualify as personal data under GDPR. Article 6 requires a legal basis for processing them. CCPA has its own disclosure requirements for California businesses above the revenue threshold. As of mid-2026, no major privacy regulator has published guidance specifically about QR code tracking, but the general rules for IP-based tracking apply.
In 2021, the UK's ICO fined Tested.me £8,000 after the company sent 83,904 marketing emails to people who had scanned QR codes at venues for COVID contact tracing. The fine was for repurposing the data, not for the scan tracking itself.
Mention QR code tracking in your privacy policy, collect only what you use, and never repurpose scan data for unrelated outreach.
Track your QR code scans with QRlfy
QRlfy's Pro tier ($9/month, or $7/month billed annually at $84/year) includes scan analytics for every dynamic code you create. Your dashboard shows scan count, location, device type, and time for each code.
Each Pro account supports up to 100 active dynamic codes with Smart Links. Smart Links add password protection, expiration dates, and device-based routing (send iPhone scanners to the App Store, Android to Google Play) behind the same printed code.
Your codes don't break when plans change. After a downgrade, every dynamic code keeps redirecting to its last destination. Editing pauses. Scanning doesn't. No ransom.
Try the generator free, no signup needed. Generate your code
FAQ
Do static QR codes track scans?
No. A static code encodes the destination directly into the pattern. Your phone reads the URL from the dots, with no server in between. No redirect means no log and no analytics.
Can I see who scanned my QR code?
You see device type and approximate location from the IP address. Not the person's identity. QR scans are anonymous unless the destination (a form, a login page) collects personal information separately.
How many scans should I expect?
Hugely variable. Uniqode's data puts restaurant table cards at 45% scan-through and retail at about 6%. Where you put the code, what's next to it, and whether there's a reason to scan all shift the number more than the code's design does.
Do I need consent to track QR code scans?
Depends on your jurisdiction. Under GDPR, IP-address logging likely needs a legal basis under Article 6. Under CCPA, California businesses above the revenue or data thresholds need a Notice at Collection. The safe default: disclose QR tracking in your privacy policy and collect only the data you actually use.