The short answer
QR code tracking records what happens when a dynamic QR code is opened. It can show how many scans were recorded, when they happened, the approximate location, and technical details such as device, browser, and operating system. It does not identify a person by name and it does not prove that a sale, booking, or form submission happened.
Tracking is most useful when each placement has its own code. A restaurant can use one code on table cards and another at the entrance. A local service business can separate a window poster from a leaflet. The dashboard then shows which placement generated the scan activity.
How QR code tracking works
A tracked QR code is dynamic. Its pattern contains a short QRtracer redirect URL rather than the final menu, form, or campaign URL. A scan follows three steps:
- The phone opens the short redirect URL.
- QRtracer records the scan event and associates it with that saved code.
- The visitor is forwarded to the current destination URL.
Because the printed pattern points to the redirect, you can change the final destination in the dashboard without changing the printed code. The destination still needs to be a working page, and the complete journey depends on the scanner's connection and the destination site.
Static and dynamic QR codes have different limits
Static QR code
A static code stores the final URL directly in its pattern. It is suitable for a stable link when you do not need QRtracer scan analytics or destination edits. Once printed, its encoded URL cannot be changed.
Dynamic QR code
A dynamic code stores a managed redirect. Choose this before printing when you need scan records, an editable destination, or separate codes for separate placements. A static code cannot be converted into a tracked code after it has been printed.
What the dashboard shows
- Total scans: every recorded open, including repeat scans.
- Estimated unique scans: an approximation of distinct scanners based on available technical signals, not an exact count of people.
- Time: when scan events occurred, useful for comparing days and campaign periods.
- Approximate location: country and city estimates derived from network information. These can be imprecise, especially on mobile networks or VPNs.
- Device details: device category, browser, and operating system inferred from the request.
These fields describe the scan request. They do not include a scanner's name, email, contacts, camera roll, or GPS position.
Example: compare a menu, form, and booking sign
Imagine a café uses three printed placements. A table card opens the menu, a receipt card opens a feedback form, and a window sign opens the booking page. Give each placement its own named dynamic code:
- Menu · tables →
example.com/menu - Feedback · receipts →
example.com/feedback - Bookings · window →
example.com/book
If the menu changes, update the menu page or its destination without replacing every table card. If the window sign records many scans but the booking system shows few completed appointments, the gap is after the scan. Improve the booking page or offer; the scan total alone is not a booking total.
How to read scan results without overclaiming
- Compare like with like. Use one code per placement and compare the same date range.
- Look for patterns, not perfect counts. Estimated unique scans and approximate locations have technical limits.
- Connect scans to destination analytics. Use your form, booking, ecommerce, or web analytics to measure the outcome after the scan.
- Test the whole path. Scan the final printed proof, check the destination on mobile, and confirm that the code is named correctly in the dashboard.
New accounts include unlimited dynamic QR codes, Analytics, and QR Studio for 30 days. Existing redirects and scan recording continue after the trial; creating new dynamic codes and accessing Analytics or Studio then requires a paid plan.