Can I track scans on a static QR code?

No — static QRs go directly to the destination with no intermediary. The only way to track is to add UTM parameters to the destination URL and use Google Analytics, but you won't see scan events directly.

Are scan locations accurate?

City-level only, derived from the scanner's IP address. We never collect precise GPS. Accuracy varies — accurate to within ~50 km in most cases, less so for users on VPN or carrier-grade NAT.

How to Track QR Code Scans (Analytics Guide)

Static QR codes are invisible to analytics — once a scanner reads the code, the user goes directly to the destination and you never know it happened. Dynamic QR codes route scans through QRolling first, capturing the data before redirecting.

What gets tracked

Every dynamic scan logs:

Timestamp — exact second of the scan
Approximate location — city-level (derived from IP, no precise GPS)
Device type — iOS / Android / desktop
Browser — Safari, Chrome, etc.
Referrer — empty for direct camera scans, populated if the QR is embedded in an app or website
Unique vs repeat — based on a privacy-respecting fingerprint (no PII)

QRolling does not track personal identifiers — no names, emails, or IP addresses are stored. Scan data is GDPR-friendly and aligned with our privacy policy.

Where to find the data

Sign in to your QRolling dashboard.
Go to My QR Codes → click any dynamic code.
The Analytics tab shows scans over time, top locations, and device breakdown.
Export to CSV for BI tools (Looker Studio, Excel, Google Sheets).

What to do with the data

Optimize placement — if a poster gets 3 scans/week, move it to a higher-traffic spot.
A/B test campaigns — print two versions of a flyer with different QRs (same destination). Compare scan rates by design.
Time-of-day patterns — restaurant menu QR scans peak at 12:30 and 19:00? Schedule social posts around those windows.
Geographic insights — if 40% of scans come from one city, run a local campaign there.

Combining with Google Analytics

QRolling's scan analytics tracks the scan event. Google Analytics tracks what the user does after arriving at your site. Combine them by:

Append UTM parameters to your dynamic QR's destination: https://yoursite.com/?utm_source=qr&utm_medium=poster&utm_campaign=spring2026
View QRolling for scan counts, GA for conversion data on those sessions.

This gives you the full funnel: scans → site visits → conversions.

Privacy and consent

If you're embedding a QR on a marketing piece distributed in Europe/the UK, the scan tracking itself is fine (no PII), but the destination page must comply with GDPR cookie consent if it loads tracking scripts. Both QRolling and your destination need a cookie banner — see our cookie policy for what we collect.