What QR code tracking measures
Every scan of a dynamic code is logged, and the analytics report turns that into four things you can act on: how many scans a code has received, how those scans are spread over time, what kind of device did the scanning, and the approximate location of the scan. You can read the analytics for a single code, or roll several codes into one campaign so the report compares placements against each other across a marketing campaign. Codes need to be dynamic for any of this to work, which you can set up in the dynamic QR code generator.
How to read your QR scan report
Six steps to go from raw scan counts to a report you can act on.
Open your dashboard
Open your dashboard and select the code or campaign you want to look at.
Set the date range
Set the date range to the period the code was live, such as the weeks a poster was up.
Read total scans first
Read total scans first, then the scans-over-time chart to find when interest peaked.
Check the device split
Check device split to see whether people are scanning on phones in the field or on desktop from a screenshot.
Compare against other codes
Compare against your other codes for the same campaign to see which placement earned the scans.
Export the data
Export the data if you need to put it in a report or alongside sales figures.
How to compare campaigns and print runs
The comparison only works if you set it up before printing. Use one code per placement rather than one code on everything, so the analytics can tell a table tent from a window poster. Name codes for where they will physically live, not for the destination, because you will be reading the report weeks later. Add consistent UTM tags to the destination URL so scan data lines up with your web analytics and the rest of your marketing campaigns. If you are testing two designs or two offers, change one thing at a time and give each version its own code, then compare the two campaigns side by side once both have run for the same number of days.
What tracking cannot tell you
QR code tracking counts scans, not identities. It will not tell you the name, email address, or phone number of the person scanning, and location is approximate rather than an exact position. A scan also does not guarantee someone stayed on the page, so pair scan counts with what happens on the destination if you care about conversion. Repeat scans from the same person can inflate totals, which matters most on codes people scan more than once, such as menus.
Tracking for teams
If several people need the same numbers, shared reporting and exports keep everyone working from one source rather than screenshots. Teams that need seats, roles, and support can run tracking through QRStuff Enterprise.
English (US)
English (UK)
French (FR)