QR code analytics explained: scans, visitors, devices, places

QR code analytics is the record of what happened after someone pointed a camera at your code: how many scans, how many people, when, on which devices, and roughly where. Every dynamic AriaQR code collects that record with no cookies and no permission prompts. This post explains each number and what a marketer actually does with it.

How does QR code tracking work?

A tracked code does not point straight at your website. It encodes a short AriaQR link. When a phone scans it, the phone opens that link, AriaQR records the visit, and the phone is sent on to your real destination in the same moment. The person scanning sees your page. You see a scan.

That is the whole mechanism, and it is why only dynamic codes can be tracked. A static code, such as a Wi-Fi code, bakes its payload straight in and never touches a server, so there is nothing to count. The trade-off is covered in dynamic vs static QR codes. For anything that opens a link, dynamic is the default on AriaQR, and tracking comes with it.

Because the redirect is where the counting happens, the code image itself carries no analytics. You can restyle it, print it at any size, or place it inside a poster, and the numbers keep flowing to the same dashboard.

What is the difference between scans and unique visitors?

Total scans is the raw count. Every time the short link is opened, it goes up by one. It includes the same person scanning twice, and it includes you testing the print.

Unique visitors is the number of distinct people behind those scans. AriaQR works this out in a privacy-preserving way, without cookies and without storing anything that identifies a person. Two hundred scans from fifty visitors is a very different result from two hundred scans from two hundred visitors.

What a marketer does with the pair:

• A high scans-to-visitors ratio on a menu or a Wi-Fi sign is normal. People come back.
• A high ratio on a print ad usually means the landing page did not load well and people tried again. Check the Devices screen before blaming the creative.
• A ratio near one means each scan is a new person, which is what you want from a poster or a billboard.

Treat unique visitors as reach and total scans as activity. Report both, and say which one you mean.

What do scans per day and the hour heatmap tell you?

Scans per day is the timeline. It shows when a campaign started to work, when it peaked, and when it went quiet. It also shows the moment a code went up, because the first scans are usually yours.

The hour-of-day heatmap is the same data folded into a 24-hour clock, in the scanner's local time. A code on a bus shelter in Chicago shows Chicago hours, not yours. That matters when you are reading a code that travels, such as one on packaging shipped across time zones.

Uses that come up again and again:

• A restaurant sees two peaks, lunch and dinner, and schedules a menu update for the gap between them.
• An event planner sees scans clustered in the hour before a session and moves the code from the back of the program to the front.
• A brand team spots that scans on a retail display happen mostly on weekends and stops paying for weekday staff to restock the leaflets next to it.

If you want the raw rows, the CSV export gives you every scan with its timestamp so you can build your own chart.

Which devices and apps are people scanning with?

The device and OS split tells you whether scanners are on iPhone or Android and which version. That is enough to catch a landing page that only breaks on one platform.

The more useful signal is in-app browser detection. When a code is scanned from inside Instagram, WhatsApp, or a similar app, the page opens in that app's built-in browser rather than Safari or Chrome. Those browsers block some things, log people out of your site, and make downloads awkward. If a third of your scans arrive through Instagram's browser, an app-download link or a checkout flow will underperform, and the fix is on your page, not on the code.

Desktop scans show up too. They are usually someone opening the link from a screenshot or an email rather than a camera, which is worth knowing when a code lives on a slide or in a PDF.

How accurate is QR code scan location?

Honest answer: approximate. AriaQR does not ask the phone for its location and never shows a permission prompt. The place comes from the network address the phone connects through. That gives a country reliably, a region or city most of the time, and a postal code when the network provides one. Sometimes, on a mobile carrier or a VPN, it resolves only to a country or to the carrier's hub city.

So the map is a picture of where your audience is, not proof of which street corner they stood on. Read it at the level it supports:

• Country and region are solid. Use them to decide where to ship, translate, or run the next campaign.
• City is good enough to compare a poster in one town with a poster in another.
• Postal code, when it appears, is a hint, not a fact.

The map clusters nearby scans together, so a hundred scans across one city show as one number until you zoom in. The countries, cities, and postal-code tables under it give the same data as lists. If you need to know which exact poster was scanned, location will not tell you. Give each poster its own code and compare them with placements.

Which metric answers which question?

Tools like Bitly and Canva report scan counts too, and they are fine when a count is all you need. The full walkthrough of each AriaQR screen is in inside the analytics dashboard.

Where to start

Make one dynamic code, print it small, and scan it from three phones. Watch the scans, visitors, device split, and city appear. Then set up a real campaign with a placement per location and let the comparison, not the raw count, tell you what to do next. Accounts are optional, but signing in keeps every code and its numbers in one place. When you need more than one code, see pricing.