QR Code Analytics
QR code analytics is the collection and reporting of data generated each time someone scans a QR code, including scan counts, time, approximate location, and device type. It turns a printed or on-screen code into a measurable marketing channel. QR code analytics only works on dynamic QR codes, because the data is logged by a redirect server that sits between the scan and the destination page.
Why QR Code Analytics Matters
Without analytics, a QR code is a one-way door. People walk through it, and nobody counts them.
Print, packaging, events, and out-of-home ads have always been hard to measure. A QR code is often the only digital touchpoint on those channels, so its scan data is the only direct evidence that a flyer or poster did anything.
QR analytics answers three practical questions:
- Did it work? Scan volume shows whether anyone engaged at all.
- Where did it work? Separate codes per placement show which poster, table tent, or package drove the scans.
- Is it worth reprinting? Scans tied to conversions show cost and revenue per scan.
Scale makes this worth doing. Statista forecast that about 99.5 million US smartphone users would scan a QR code in 2025.
What QR Code Analytics Tracks
Most QR analytics tools report the same core set of QR code statistics:
| Metric | What it measures | Source of the data |
|---|---|---|
| Total scans | Every scan request, including repeats | Redirect server log |
| Unique scans | Distinct devices that scanned | IP address plus device signature, deduplicated |
| Scan time | Date, hour, and day of week | Server timestamp |
| Location | Country, region, and city | IP geolocation |
| Device and OS | iPhone or Android, OS version, browser | User-agent string |
| Sessions and conversions | What happened after the scan | UTM parameters read by Google Analytics 4 |
Two limits apply. Location is inferred from the IP address, not GPS, so it is usually accurate to the city at best and can point to a mobile carrier hub instead. Unique scans have no industry standard, so each vendor decides how long a device counts as “the same scanner”. Unique scan numbers from two different tools are not comparable.
How QR Code Tracking Works
QR code tracking relies on a redirect. A dynamic QR code encodes a short URL that belongs to the tracking service, not the final page.
- The phone camera decodes the short URL and opens it.
- The tracking server logs the request: timestamp, IP address, and user agent.
- The server returns a redirect (usually HTTP 301 or 302) to the destination URL.
- The destination loads, and any UTM parameters on it pass campaign data to your web analytics.
The encoded URL and the destination look like this:
Encoded in the code: https://go.example.com/spring-flyer
Destination: https://example.com/sale?utm_source=flyer&utm_medium=qr&utm_campaign=spring-2026
A static QR code encodes the destination directly. No server sits in the middle, so nothing logs the scan. The only way to measure a static code is to put UTM parameters in its URL and read the resulting sessions in GA4. That shows visits, not scans, and the code can never be edited after printing. The full setup, including GA4 configuration, is covered in this guide to QR code tracking.
QR Code Scans vs Website Sessions
QR code scans and website sessions are different units, and they never match exactly. A scan is a request to the redirect server. A session is a page load where the analytics tag fired.
Scans usually run higher than sessions. Common reasons:
- The visitor closes the browser before the page finishes loading.
- A cookie consent banner or ad blocker stops the GA4 tag from firing.
- One person scans twice within 30 minutes, which GA4 counts as one session.
- The redirect drops the UTM parameters, so the visit lands in direct traffic.
Divide sessions by scans to get a scan-to-session rate. A sudden drop in that rate usually points to a slow landing page or a broken redirect, not lost interest.
Frequently Asked Questions
Can you track scans on a static QR code?
No. A static QR code sends the phone straight to the destination, so no server records the scan. You can add UTM parameters to the encoded URL and measure the resulting sessions in Google Analytics 4. That shows visits but not raw scans, and you cannot change the URL once the code is printed.
How accurate is QR code scan location data?
QR code scan location is approximate. It comes from IP geolocation, which is usually reliable at the country level and often accurate to the city. Mobile networks route traffic through regional hubs, so a scan in a small town can appear under a larger nearby city. No mainstream QR analytics tool reads GPS without the visitor granting permission on the landing page.
What is the difference between total scans and unique scans?
Total scans count every scan request, including the same person scanning several times. Unique scans count distinct devices, usually by combining IP address and device details within a time window the vendor sets. Use total scans to measure reach of a placement and unique scans to estimate how many people engaged.
Does QR code analytics work with Google Analytics?
Yes, but GA4 does not see the scan itself. The redirect server counts the scan, and GA4 only records the session after the landing page loads. Add utm_source, utm_medium=qr, and utm_campaign to the destination URL so those sessions are attributed to the right campaign instead of direct traffic.
To create dynamic codes that report scans next to your other link analytics, use linkutm’s QR codes feature.