QR Code Analytics — Scan Tracking, Attribution & CSV Export

Timestamp, country, city and region, device type, browser, operating system, referrer, the final landing URL, and all five UTM values (source, medium, campaign, content, term). Each scan also carries an anonymous visitor ID and a session ID so repeat scans are distinguishable from first-time ones, plus the variant name when A/B testing is active. No name, email, phone number or precise location is captured, because a redirect has no access to any of it.

No. The redirect responds first and the scan is written afterwards, outside the request that the visitor is waiting on. The scanner gets its redirect immediately, and the analytics write happens in the background. The redirect also carries an X-Robots-Tag noindex header so tracking URLs never enter search results.

No, and neither can anyone else. A static code encodes the destination directly in the black-and-white pattern, so the phone goes straight to your site with no intermediate step to count. There is nothing to instrument. If you need scan data, the code has to be dynamic before it goes to print. The one partial workaround is putting a UTM-tagged URL inside a static code, which gives you GA4 sessions without scan-level detail, and locks those UTM values into the printed pattern forever.

City-level and directional. Location is derived from the IP address at the edge, not from device GPS, because a web redirect cannot request location permission. Mobile carriers frequently route traffic through gateways in another city, and corporate VPNs will place a scan in whichever country the exit node sits. Country data is reliable enough to act on. City data is useful in aggregate and wrong often enough that you should not build a decision on a single row.

Yes, if you set UTM parameters. EZQR forwards them to the destination URL, so GA4 attributes the session to your campaign instead of filing it under direct traffic. The two systems count different things and will not match exactly: EZQR counts redirects, GA4 counts sessions that finished loading. Scans where someone closes the browser mid-load appear in EZQR and never reach GA4, so EZQR totals normally run slightly higher.

Lite at $5/month includes a 30-day scan history. Pro at $10/month adds full historical analytics, CSV export, A/B testing and geo-targeting. Max at $20/month adds REST API access, an audit log and weekly email reports. All prices are monthly billing, not annual. The free plan includes 3 dynamic codes without the analytics dashboard, and unlimited static codes that cannot be tracked by design.

Export it first. Scan history is tied to the dynamic codes on your plan, and dynamic codes stop redirecting when the subscription ends, which also ends new data collection. CSV export on Pro and above exists precisely so the history is portable. Static codes are unaffected because they were never tracked and never depended on the redirect.

No, and be sceptical of any vendor implying otherwise. A scan is an anonymous HTTP request. It carries an IP address, a user-agent string and whatever UTM values you attached, none of which identify a person. Identity only enters if the destination page asks for it — a form, a login, a checkout. The QR measures that someone scanned. Your landing page is what learns who.