Skip to main content
EZQR

Analytics QR Code

QR Code Analytics — Scan Tracking, Attribution & CSV Export

Every scan of a dynamic QR passes through a redirect, and the redirect is what records it. Timestamp, city, device, browser, referrer and full UTM set — exported to CSV or pulled through the API.

Free static QR codes. Sign up to unlock dynamic codes & analytics.

Your QR code will appear here

About Analytics QR Codes

QR code analytics answer one question: did the print work? A dynamic QR encodes a short redirect URL, and every scan passes through that redirect before landing on your destination. The redirect is the measurement point. It records the scan, then forwards the visitor.

That mechanism sets a hard boundary most vendor pages skip. A static QR cannot be tracked at all. Its destination is encoded directly in the module pattern, so the scan goes phone-to-website with nothing in between to count it. No vendor can track a static code. That is physics, not a paywall, and any tool claiming otherwise is either quietly converting your code to a dynamic one or counting something else.

Walkthrough

How to Create a Analytics QR Code

  1. Create the code as dynamic, not static

    Analytics require a redirect, so the code has to be dynamic from the start. Pick a dynamic QR when you create it. Converting later means reprinting, because the encoded pattern changes.

  2. Add UTM parameters if you use GA4

    Set utm_source, utm_medium and utm_campaign on the destination. EZQR appends them to the forwarded URL, so the same scan appears in both EZQR and your Google Analytics property. Without UTMs, GA4 files QR traffic under direct.

  3. Print, place, and label the placement

    Give each physical placement its own code. One code across ten locations produces a single number that cannot tell you which of those ten locations earned it, which is the question you printed the code to answer in the first place. Ten codes produce ten numbers, and the comparison between them is the actual insight.

  4. Read the dashboard

    Scans appear with timestamp, city and country, device type, browser and operating system, referrer, and any UTM values you attached to the destination before printing. Totals and unique counts are shown separately, because the gap between them is what tells you whether one person scanned repeatedly or many people scanned once.

  5. Export to CSV or pull through the API

    Pro exports full scan history to CSV. Max adds REST API access so scan data lands in your warehouse or BI tool without a manual download.

Where it works

Analytics QR Code Use Cases

Print attribution — which flyer, poster or packaging placement actually produced scans, compared placement by placement.

Multi-location retail, giving each store its own code so branch performance is comparable rather than pooled.

Campaign A/B testing, splitting scans across two destinations from a single printed code and reading conversion per variant.

Event and conference measurement — scans by hour reveal when a booth was actually busy.

Direct mail response rate, where the QR is the only measurable response channel on the piece.

Restaurant menus, where scan volume by table or time-of-day informs staffing.

Agency client reporting, where scan data is the deliverable proving a print campaign moved.

Geographic testing — country and city breakdown showing whether a national campaign performed evenly.

What works in practice

Analytics QR Code Best Practices

Use one code per placement, not one code per campaign. A single QR on every asset collapses ten questions into one number. Separate codes cost nothing and make the comparison possible.

Set UTM parameters before printing. They pass through to the destination and reconcile EZQR scans with GA4 sessions. Adding them after the print run means the printed codes never carry them.

Treat unique scans as approximate. Uniqueness is derived from a browser cookie. Clear the cookie, switch phones, or scan in a private window and the same person counts twice. Total scans are exact; unique scans are an estimate.

Do not expect GPS. A redirect sees an IP address, which resolves to city level at best and to the wrong city on mobile networks routing through a distant gateway. City and country are directional, not precise.

Keep a static fallback for anything safety-critical. Analytics require a vendor redirect, which is a dependency. For codes that must never break, static is the safer choice and the trade is that you lose measurement.

Export before you downgrade. Scan history on Lite covers a 30-day window. Pull the CSV before the window closes or the plan changes.

Compare like for like on time. A code printed in March and one printed in June have different exposure. Normalise by days-in-market before concluding one placement beat the other.

Analytics QR Code FAQ

Common questions about generating, printing, and deploying these codes.

Related Articles

Related Industries

Related Guides

Related Tools

Ready to create your Analytics QR code?

Free, no watermarks. Generate and download in seconds.

Generate Free QR Code