arrow_backBlog
·5 min read·Super QR Code Generator Team

QR Code Analytics: 6 Metrics That Actually Drive Decisions

Stop obsessing over total scans. Learn the 6 QR code analytics metrics that reveal what's working, what's wasted, and where to act next.

qr code analyticsqr code trackingdynamic qr codes
QR Code Analytics: 6 Metrics That Actually Drive Decisions
AI-generated

Most QR code dashboards show you a big number — total scans — and not much else. That number feels good but rarely tells you whether your campaign is working or where your budget is going to waste. These six metrics cut through the noise and give you something to act on.

Why "Total Scans" Is a Vanity Metric

Total scans counts every tap, including duplicate scans from the same person, accidental reads, and your own test scans during setup. It inflates your sense of performance. The metrics below separate signal from noise.


1. Unique Scans vs. Repeat Scans

What it is: Unique scans count individual devices (proxied by IP + user agent); repeat scans count return visits from the same device.

Why it matters: A flyer at a trade show should show mostly unique scans — each person scans once. A restaurant table tent, by contrast, should show repeat scans from regulars. If your table tent shows almost no repeats, your loyalty loop may be broken.

Action: Compare unique-to-total ratio across placements. A ratio below 1.2 (nearly all unique) is normal for one-time contexts. A ratio above 2.0 on a reusable asset suggests genuine re-engagement.


2. Scan-to-Conversion Rate

What it is: The percentage of scans that complete a defined action — a form fill, purchase, menu view, coupon redemption, or app download.

Why it matters: This is the metric that connects your QR code to revenue. High scan counts with a 0.5% conversion rate is worse than modest scan counts with a 12% conversion rate.

How to set it up: Most dynamic QR platforms let you append UTM parameters to your destination URL. Pair that with a goal in Google Analytics 4 (or a simple thank-you page redirect) and you can calculate conversions per QR source automatically.

Action: If scans are strong but conversions are low, the problem is almost always the landing page — not the QR code itself.


3. Time-of-Day and Day-of-Week Distribution

What it is: A breakdown of when scans happen across hours and days.

Why it matters: Timing data reveals which placements are actually being seen. A poster in a coffee shop should peak between 7–9 AM and 3–5 PM. A QR code on a direct mail piece typically spikes in the first 72 hours after delivery, then drops sharply.

Context Expected peak
Restaurant table Lunch and dinner hours
Retail shelf tag Weekends, 11 AM–3 PM
Direct mail Days 1–3 post-delivery
Event badge During and 24h after event
Social media link Within hours of posting

Action: If scan timing doesn't match expected foot traffic patterns, the placement may have poor visibility — relocate or resize the code.


4. Device and OS Breakdown

What it is: The split between iOS and Android (and occasionally desktop) among scanners.

Why it matters: This affects destination experience. If 70% of your scanners are on iOS but your landing page uses a feature that breaks on Safari, you're losing most of your audience silently. It also informs app-download campaigns — if you're pushing an Android app but 80% of scanners are iPhone users, your placement is in the wrong channel.

Action: Check device split before any A/B test on the landing page. Run separate mobile experience audits for each major OS in your mix.


5. Geographic Distribution (City/Region Level)

What it is: Where scans are originating, typically down to city or region.

Why it matters: For multi-location businesses or campaigns running in several markets, geography tells you which locations are driving engagement and which aren't. A QR code on packaging distributed nationally should show spread across regions. A QR code in a single-city billboard campaign should show tight geographic clustering — if it doesn't, the scans may be bot traffic or someone photographing the ad without intent.

Action: Flag any geographic anomaly early. Sudden spikes from unexpected cities can indicate scraping, bot activity, or (occasionally) press coverage you didn't anticipate.


6. Scan Velocity (Rate of Change Over Time)

What it is: How quickly scan volume is rising or falling over a defined period — not the absolute count, but the trend.

Why it matters: Absolute scan counts tell you history. Velocity tells you trajectory. A campaign with 200 scans/day growing at 15% week-over-week is healthier than one with 500 scans/day declining at 20% per week. Velocity also signals the natural decay curve of physical media: most print placements peak within the first week and decay exponentially.

How to calculate it: Pull weekly totals from your analytics dashboard. Divide this week's total by last week's. Subtract 1 and multiply by 100 for a percentage change.

Action: Set a minimum acceptable velocity threshold before launching (e.g., "this campaign must not drop below 50 scans/day before week 4"). Use it as a trigger to refresh creative or reposition the placement.


Setting Up a Practical Tracking Stack

You don't need enterprise software to track all six metrics. Here's a lean setup:

  • Dynamic QR codes (required — static codes are untraceable): Use a generator like Super QR Code Generator that includes built-in scan analytics.
  • UTM parameters on your destination URL: Cover source, medium, and campaign at minimum.
  • GA4 or equivalent: Track goal completions tied to each UTM source.
  • A simple weekly report: Export scan data + UTM-attributed conversions into a spreadsheet. Calculate conversion rate, velocity, and device split in three columns.

Total setup time: under 30 minutes. This is enough to make real decisions.


Key Takeaways

  • Total scans is a starting point, not a conclusion. Unique scans, conversion rate, and velocity are far more actionable.
  • Conversion rate is the bridge between QR performance and business outcomes. A low rate almost always points to a landing page problem, not a scanning problem.
  • Time-of-day data validates whether your placement matches your audience's behavior. Mismatched peaks mean visibility issues.
  • Device breakdown prevents silent UX failures. Always test your destination on the dominant OS in your scan data.
  • Geographic anomalies are worth investigating quickly — they can indicate bot traffic or unintended distribution.
  • Velocity tells you where a campaign is headed, not just where it's been. Set a floor and act when you hit it.