How to Track How Many People Scanned Your QR Code
Tracking QR code performance means combining platform-level scan counts with UTM-tagged destination data to see who scanned and what they did next.
Elena Ruiz
Offline & Retail Marketing Specialist
QR Code Marketing Blueprint Guide
How do you actually track how many people scanned a QR code?
Tracking QR code scans requires two complementary layers used together: a dynamic QR code platform's built-in scan analytics, which counts how many times the physical code was scanned, and UTM parameters on the destination URL, which show what those scanners did once they landed on your website. Using only one layer gives an incomplete picture of performance.
Why is a dynamic QR code required for tracking?
Static QR codes encode a destination directly into their pattern with no server involved, which means there's no mechanism to log or count anything, from a tracking standpoint, a static code is a complete black box. Dynamic QR codes route scans through a server-hosted redirect, and it's this server-side step that makes counting and logging scans technically possible in the first place.
What does platform-level scan tracking show you?
Most dynamic QR code platforms provide built-in scan analytics as a core feature, typically showing total scans over time, plus additional detail like approximate geographic location (based on IP address), device type, and the date and time of each scan. This gives a direct, platform-reported count of raw scan volume, independent of anything happening after the scan on your own website.
How do UTM parameters add a second layer of tracking?
Tagging the destination URL behind your dynamic QR code with parameters like utm_source=qr_code, utm_medium=print, and a specific utm_campaign identifying the exact placement (flyer, packaging, poster, business card) gives you visibility into that traffic within your main analytics platform, alongside all your other tracked channels, showing whether scanners actually did anything meaningful once they landed.
Why do you need both layers rather than just one?
The platform-level scan count tells you how many times the physical code was scanned; the UTM-tagged data tells you what happened afterward, whether scanners stayed on the page, browsed further, or completed a meaningful action. Scan counts alone don't reveal whether traffic converted into anything valuable, while UTM data alone makes it harder to calculate what percentage of actual scans successfully converted into a tracked website visit.
How do you set up conversion tracking on the destination page?
Define a specific conversion event on your destination page within your analytics platform, a form submission, a purchase, a signup, so you can see not just how many people visited from the QR code, but how many completed the action you intended it to drive. This transforms a raw scan count into an actual return-on-investment calculation, especially valuable when comparing performance against the cost of the print materials the code appeared on.
How do you compare performance across multiple QR code placements?
If you're running QR codes across multiple placements at once, one on packaging, one on a flyer, one on a poster, use distinct utm_campaign or utm_content values for each placement to directly compare their performance within the same unified report, revealing which physical placement is actually driving the most engagement.
What are the most common QR code tracking mistakes?
A frequent mistake is using a static QR code and only realizing after the fact that no scan data was ever being collected, at which point the material is already printed with no ability to retroactively add tracking. Another common issue is using a dynamic code correctly but forgetting to add UTM parameters to the destination URL, meaning the platform-level scan count exists but that traffic shows up in your main analytics platform as generic, unattributed traffic.
What should a QR code tracking checklist include before deployment?
Before deploying any QR code you intend to measure, confirm you're using a dynamic QR code platform with scan analytics enabled, that the destination URL is properly UTM-tagged with source, medium, and a specific campaign or content value identifying this exact placement, and that a relevant conversion event is configured on the destination page if driving a specific action is the code's actual goal.
Frequently Asked Questions
Can you track scans on a static QR code?
No. Static codes have no server or redirect involved, so there is no mechanism to log or count scans. Tracking requires a dynamic QR code from the start.
Why do I have a scan count but no matching website traffic?
This usually means the dynamic code is working but its destination URL is missing UTM parameters, so the traffic lands in your analytics platform as generic, unattributed traffic rather than being tied to the QR code campaign.
What UTM parameters should every trackable QR code include?
At minimum, utm_source (e.g. qr_code), utm_medium (e.g. print), and a specific utm_campaign or utm_content value identifying the exact placement, such as a particular flyer, poster, or packaging run.
Join 14,000+ marketing growth leaders
Receive our bi-weekly breakdown of campaign analytics setups, attribution rules, naming tactics, and link-stitching blueprints. Direct to your inbox.
Continue reading blueprints
All ArticlesDynamic QR Code Tracking Explained
A dynamic QR code doesn't store your destination at all, it stores a pointer. That single design decision is why tracking, editing, and analytics all become possible.
How a Dynamic QR Code Generator Actually Works
Behind every dynamic QR code is a small piece of redirect infrastructure doing the actual work. Here's what a generator builds when you click create.