How analytics work
Scans, devices, countries, browsers, the heatmap, and what each panel actually counts.
Every scan of a dynamic QR code is recorded as a row in our analytics database. We capture timestamp, country, city, device class (mobile / tablet / desktop), OS, browser, and HTTP referrer.
Open any QR's detail page → Analytics. The header lets you switch between 7-day, 30-day, and 90-day windows. Each chart re-bucketing is computed in your browser's timezone — so the "Wednesday at 9 PM" cell on the heatmap means 9 PM in your local time, not UTC.
The "scans over time" chart aggregates by day. Countries, devices, OS, and browsers are top-N tables. The 7-by-24 heatmap shows which weekday-and-hour combinations are hot.
IP addresses are not stored as plaintext — we keep a one-way SHA-256 hash per scan so you can deduplicate without us holding raw addresses. The hash is consistent within a scan window so the dashboard counts unique visitors, but it's not reversible.
Workspace-level analytics at /analytics roll up across all your QRs. Per-QR analytics at /qr/<id>/analytics drill into one code.
Still need a hand?
Email support@qra.cc