05 · Analytics
Every dynamic QR code streams scan data into your dashboard in real time. Forensic detail, not just totals.
Every scan
Each scan is a row: timestamp, country, city, device, OS, browser, and referrer.
Filters
Compare campaigns, cross-check placements, spot the surprise winner.
Export
Pipe raw scan data into your BI stack whenever you want.
Workflow
Scan data only changes decisions when someone looks at it on a schedule. Here is the cadence that works.
Confirm the code is dynamic and the destination carries UTMs, so scans show up in both QR Lift and your web analytics.
Record week-one scans per placement. Everything after is measured against this, not against a hopeful target.
Device split tells you about the audience; geography tells you whether assets ended up where you shipped them.
The useful question is which surface earns scans — window, table, packaging, receipt — because that's what you can change next time.
Push raw scan rows into your BI tool so QR performance sits next to the rest of the funnel instead of in a silo.
One short readout: top placements, dead codes, and destinations worth repointing. Then act on it.
Best practices
Ways to keep the numbers honest.
Your own team scans the code during QA. Note the launch date so the first hours don't skew the baseline.
Menus and info codes get rescanned by the same people. That's a signal, not noise — just don't read it as unique reach.
Changing destination mid-campaign breaks comparability. If you must, mark the date in the readout.
Aggregate views change; raw scan rows are your record. Export before you archive a campaign.
Country and city are inferred from the scanner's IP. Country is near-perfect; city is close for most, less reliable on cellular networks.
No. We capture the browser's User-Agent and the IP for geo lookup — no cookies, no fingerprinting, no cross-site tracking.
No — static codes go directly to the destination without passing through us. That's why dynamic codes exist.