marketing

QR Code Analytics: What to Track and How (2026 Guide)

QR code analytics in 2026: the exact scan metrics to track, how dynamic QR codes capture data, the UTM setup that ties scans to revenue, and the mistakes that leave money on the table.

Team U2L • 18 min read

QR code analytics is the practice of capturing and reporting on scan data from dynamic QR codes so you can see who scanned, where, when, what device they used, and what happened after. Only dynamic QR codes carry analytics because they redirect through a short link that logs every scan. Combined with UTM parameters and a downstream tool like GA4, scan data becomes a full attribution funnel from the physical placement to the eventual conversion.

QR code analytics is the process of capturing scan events from dynamic QR codes and reporting them as time-stamped data points, including location, device, operating system, browser, and referrer, so a marketer can measure which physical placement drove which mobile interaction.

You've printed 5,000 flyers. Two weeks later, the marketing lead walks in and asks, "How many people actually scanned that QR code?" If you can't answer within thirty seconds with a real number, a location breakdown, and a device split, your QR campaign is being measured by vibes. Every one of those flyers is a data point you're not collecting.

The uncomfortable truth is that most QR code campaigns die not because the code failed to scan but because nobody set up the analytics layer before the print job went out. Once the code is printed as a static image, the game is over. There's nothing to instrument. This guide fixes that. We'll cover the exact metrics that matter, how a dynamic QR code captures them, the UTM setup that connects scans to downstream conversions, how to compare placements without guessing, and the mistakes that quietly ruin campaign attribution. By the end, you'll have a working QR analytics stack you can actually report from.

Table of Contents

What Is QR Code Analytics?

QR code analytics is the layer of data collection that sits between a scan and the destination page. When a phone camera reads a dynamic QR code, the code contains a short redirect URL. The scanner's browser hits that short URL, the redirect server captures a set of metadata about the scan (time, geographic region derived from IP, device, OS, browser, referrer), then forwards the user to the actual destination. Everything captured in that split-second handoff becomes a row in your analytics dashboard.

This is the same mechanism URL shorteners have used for over a decade to track link clicks. A dynamic QR code is really just a scannable wrapper around a short link. Every insight you'd get from tracking a link click, you also get from a QR scan, plus the added benefit of knowing the click originated from an offline placement.

The reason this matters: offline marketing was famously unmeasurable for a hundred years. Print ran, billboards posted, packaging shipped, and marketing teams stared at total sales numbers wondering which channel deserved credit. QR analytics closes that gap. Every physical surface with a QR code becomes a trackable click, with a timestamp, a location, and a path forward through the funnel.

Why Only Dynamic QR Codes Can Be Tracked

If you take one thing away from this article, take this: static QR codes generate zero analytics, forever. A static QR encodes the destination URL directly into the black-and-white pattern. When someone scans it, their phone goes straight to that URL. No server ever sees the scan. No log, no metadata, no report.

A dynamic QR code encodes a short URL instead (something like u2l.ai/spring-menu). When someone scans, the request hits a redirect server first, gets logged, then forwards to your real destination. That log entry is the entire foundation of QR analytics. Without it, there is no data.

The problem is that free QR generators often default to static codes because they cost less to serve (no redirect infrastructure needed). You paste in a URL, download a PNG, and unless the tool explicitly says "dynamic," you're getting a static code with no measurement layer. Six weeks later when someone asks for scan numbers, the honest answer is: we have none.

Our full breakdown lives in the dynamic vs static QR codes explainer, but the practical rule is simple. Any QR code on any marketing surface should be dynamic. The rare exceptions (Wi-Fi credentials, vCards for contact sharing) are cases where you want the data self-contained inside the code. For anything you'd want to measure, dynamic is the only option.

U2L AI generates dynamic QR codes on top of short URLs by default, so every code you make is trackable from the first scan. You can even generate one at u2l.ai without creating an account, and add analytics access later by signing in. (Disclosure: U2L AI is our product.)

The 7 Metrics Every QR Code Should Track

Not all analytics dashboards capture the same fields. Here's the set that actually matters for making decisions, and why each one earns its space:

1. Total scans. The headline number. Every campaign report starts here. But total scans alone is dangerous, because it lumps repeat scanners into the same bucket as new ones. Always look at total scans alongside unique scans.

2. Unique scans. How many distinct visitors hit the code. This is the closer approximation of "how many people did this reach." Repeat scans matter for behaviors like loyalty check-ins, but for reach analysis, unique is the number to trust.

3. Geographic location. Country and city, derived from the scanner's IP address. This is where QR analytics quietly earns its keep for multi-location businesses. A restaurant chain can see which stores' table tents are actually being scanned. A trade show marketer can compare booth performance across cities. Note the caveat: VPN users show the VPN server's location, not their real one, so the data is directionally accurate but never perfect.

4. Device type. iOS vs Android vs desktop. Post-scan destinations often perform differently by device, so a device split lets you route iOS scans to the App Store and Android scans to the Play Store, or serve up different landing pages entirely.

5. Operating system and browser. More granular than device. Useful when a landing page starts underperforming on a specific browser version, or when an in-app browser (Instagram, TikTok) is causing conversion drops that show up in the browser field.

6. Time of day and day of week. Peak scan windows tell you when your audience actually interacts with the code. A packaging QR peaks in the evening (unboxing at home). A table-tent QR peaks around lunch and dinner service. Time-of-day patterns are the input that shapes when you should update destinations, launch new offers, or push promoted content.

7. Referrer and campaign attribution. When UTM parameters are appended to the destination URL, the click flows into downstream tools like GA4 as an attributed session. This is the metric that connects a physical scan to a specific line in a marketing report.

These seven together answer the questions any campaign report needs to answer: how many people, where, on what device, at what time, from which placement. A dashboard that stops at "total scans" is a dashboard you can't act on.

Setting Up UTM Parameters for QR Scans

Here's where a lot of teams accidentally break their tracking. GA4 sees a QR scan as a direct visit by default, because nothing in the URL tells it otherwise. That means a great QR campaign shows up in your GA4 report as anonymous "Direct" traffic, indistinguishable from someone typing your URL from memory.

The fix is to append UTM parameters to the destination URL before you generate the QR code. A canonical UTM string for a QR placement:

?utm_source=table-tent&utm_medium=qr&utm_campaign=spring-launch-2026&utm_content=downtown-store

Break it down:

  • utm_source identifies the physical placement (table-tent, packaging, billboard-highway5, poster-cafe-window).
  • utm_medium stays as qr across every QR campaign, so you can filter GA4 by medium and see all QR traffic in one report.
  • utm_campaign groups all placements of the same promotion.
  • utm_content distinguishes between variants of the same placement (per-store, per-city, per-poster-design).

Lowercase everything. Use hyphens, never spaces. Pick a naming convention on day one and stick to it. If half your tags say Instagram and half say instagram, GA4 treats them as two different sources and your report splits in half. Our full breakdown lives in the UTM parameters guide.

Once the destination URL is UTM-tagged, generate the dynamic QR code on top of that URL. The short link inherits the UTM tags, the redirect passes them through, and GA4 sees a properly attributed session. The chain works because every layer forwards the parameters intact.

Wiring Scan Data Into GA4 and Beyond

Once UTMs are in place, GA4 becomes the second layer of your QR analytics stack. The short-link dashboard tells you what happened at the moment of scan. GA4 tells you what happened after: pages visited, session duration, events fired, conversions closed.

The setup, once, in GA4:

  1. Confirm the destination page has GA4 installed and is firing pageview events.
  2. Set up a filter or a saved report for session_medium = qr so you can pull all QR traffic in a single view.
  3. Create a conversion event for the action you care about (purchase, form submission, app install, phone call, whichever applies).
  4. Optionally, create a segment for QR-driven users and layer it into audience reports.

Marketers who standardize UTM naming conventions report meaningful lifts in campaign attribution accuracy, according to Trackingplan's 2026 report on UTM best practices. The reason is boring but important: consistent tags mean data flows into one bucket instead of ten.

Beyond GA4, most teams pipe the same data into their CRM, email platform, or attribution tool. The short-link CSV export is the bridge here. Pull scan data out of the QR dashboard, join it against your CRM by timestamp or session ID, and you have a full offline-to-online attribution path. Our complete guide to link tracking walks through the multi-tool stack in depth.

Per-Placement QR Codes: The Trick Most Teams Miss

Most QR campaigns use one code across every placement. A single QR gets printed on flyers, posters, table tents, and packaging. The result: the dashboard shows a flat count of scans with no way to know which placement drove which scan. Impossible to compare, impossible to optimize.

The fix is unglamorous. Generate one dynamic QR per placement. Each code points at the same landing page but carries its own UTM tag in the destination URL. The scan dashboard now separates data by placement, and GA4 does the same. Suddenly you can rank placements by scans, by conversions, and by revenue.

A concrete example. A regional coffee chain runs a spring loyalty promo across:

  • Tabletop cards at all 12 stores (one QR per store)
  • Receipt inserts (one QR)
  • A local newspaper insert (one QR)
  • A window poster at each store (one QR per store, distinct from the tabletop)

That's 26 dynamic QR codes, all pointing at the same signup page but each with a unique utm_content tag. Two weeks in, the chain can rank stores by tabletop scan rate, see which store's window posters outperform, spot that receipts convert better than newspaper inserts, and shift budget accordingly. Without per-placement codes, none of that is knowable.

This is where an all-in-one link and QR platform saves hours. Creating 26 codes one by one in a fragmented workflow is painful. Bulk generation via CSV upload or API is the difference between a marketing team that runs per-placement tracking and one that gives up and uses a single code. Our guide on how to edit a QR code destination without reprinting covers the other half of this workflow, which is what to do when you need to change where a printed code points.

The KPIs Marketers Actually Report On

The 2026 marketer survey on QR usage lines up around a small handful of KPIs. Based on Wave Connect's 2026 QR statistics roundup, marketers report tracking click-through rate (30%), customer engagement (30%), conversion rate (22%), and sales or revenue (12%), while a stubborn 6% still measure nothing at all. If your team is in that 6%, the fix is a one-hour setup.

The KPIs that actually earn attention in reports:

  • Scan volume by placement. Total and unique, week over week. The most basic pulse of a campaign.
  • Scan-to-visit rate. Not everyone who scans lands on the page (some scans are aborted mid-load). The ratio matters. A sudden drop here often signals a landing page performance issue.
  • Post-scan conversion rate. Of the people who scanned and landed, how many did the thing you wanted? Post-scan conversion rates typically range from 5% to 40%, depending on the action. Form fills and contact saves convert higher than checkouts.
  • Geographic distribution. Especially important for multi-location businesses running local campaigns.
  • Device split and OS mix. Feed this back into landing page optimization.
  • Time-of-day heatmap. When you should launch offers, refresh destinations, or push notifications.
  • Cost per scan. Total campaign cost divided by unique scans. Useful for comparing QR campaigns against digital ad benchmarks.
  • Cost per conversion. The ultimate ROI KPI. This is the one that makes budget conversations easy.

Not every KPI needs to appear in every report. Pick three or four that align with the campaign's actual goal, put them at the top of the dashboard, and let the rest live in a secondary tab.

Reading Your QR Analytics Dashboard

Most QR analytics dashboards follow a common shape. There's a top-line panel with total scans and unique scans, usually with a comparison to the previous period. There's a time-series chart showing scans over the last 7, 30, or 90 days. There's a geographic map or table. There's a device breakdown, an OS breakdown, and a browser breakdown. And there's a referrer view, which for pure QR traffic will mostly be blank (a scan doesn't have a traditional referrer) but will populate when the campaign traffic mixes with web sharing.

What to look for on a weekly review:

  1. Trend direction. Is scan volume climbing, stable, or dropping? A drop after week one is normal (fresh placements always spike). A drop after month one usually means either the placement is worn out or the CTA on the code has gone stale.
  2. Placement rank. Which UTM-tagged placement is winning? Any placement in the bottom quartile is a candidate for redesign, replacement, or removal.
  3. Device anomalies. If iOS conversion suddenly cratered while Android held steady, something broke on your iOS landing page.
  4. Location spikes. A city or region suddenly overperforming is often a sign of press coverage, an influencer scan, or a local trend worth investigating.
  5. Time-of-day shifts. If your peak window moves, your audience or the campaign context has changed. Adjust send times, refresh dynamic destinations, or update the CTA.

U2L AI captures geographic, device, OS, browser, referrer, and timeline data on every QR scan (when the QR is built on top of a short link), plus a unique visitors metric that separates repeat scanners from new ones. The CSV export means you can pipe the data into whatever downstream tools you already run, and your scan history stays intact for long-running campaigns. See u2l.ai/features for the current feature list.

Mistakes That Corrupt QR Code Analytics

Using static QR codes for marketing. Repeat: static codes generate zero data. Every marketing QR should be dynamic.

Skipping UTMs on the destination URL. Without UTMs, GA4 attributes QR-driven traffic to Direct, and your report shows an unexplained bump in unattributed sessions. Always tag the destination before generating the code.

Reusing the same QR everywhere. A single code across every placement erases per-placement comparison. Generate one code per placement.

Inconsistent UTM casing. Email and email are two different sources to GA4. Lowercase everything, always.

Ignoring VPN geographic bias. A meaningful share of users route through VPNs, which lands their scans at the VPN server's location instead of their own. Location data is a useful signal, not gospel. Never make decisions on tight geographic slices without acknowledging the noise.

Only measuring scans, not conversions. Scans are the funnel top. If you can't connect them to a downstream action, you're measuring the least valuable end of the pipe.

Letting destinations rot. Dynamic QR codes still need their destinations kept alive. A 404 destination burns every scan for the life of that code. Audit destinations monthly.

Overcomplicating the dashboard. More metrics doesn't mean better reporting. Pick three or four KPIs, own them, iterate. A cluttered dashboard is a dashboard nobody looks at.

Frequently Asked Questions

Can you track scans on a static QR code?

No. Static QR codes encode the destination URL directly into the pattern, so scans go straight to the destination without touching any tracking layer. You get zero analytics: no scan count, no location, no device data. To track scans, the code must be dynamic (encoded with a short URL that redirects through a server that logs each request).

What data does a QR code capture when someone scans it?

A dynamic QR code captures the scan timestamp, approximate geographic location (from IP), device type, operating system, browser, and referrer. It does not capture personal information about the scanner. With UTM parameters on the destination URL, the scan also gets attributed to a specific campaign and placement in your downstream analytics tool.

Do QR codes work with Google Analytics 4?

Yes. Append UTM parameters to the destination URL of the QR code (utm_source, utm_medium=qr, utm_campaign, utm_content). When the scan lands on your site, GA4 reads the UTMs and attributes the session correctly. Without UTMs, GA4 treats QR scans as Direct traffic and you lose attribution.

How accurate is QR code location tracking?

Location tracking is based on the scanner's IP address, which resolves to a city or region. It's directionally accurate for aggregate analysis, but individual scan locations can be off by miles, and VPN users appear at the VPN server's location. Use location data for regional trends, not for pinpoint targeting.

What's a good conversion rate for a QR code campaign?

Post-scan conversion rates typically fall in the 5% to 40% range depending on the ask. Contact saves and form fills convert higher than purchases; in-context placements like restaurant tables convert higher than passive placements like billboards. Benchmark your first campaign against itself, then optimize.

Can I track QR code scans in real time?

Yes. Most modern QR analytics platforms surface scan data in real time or near real time (usually within a minute of the scan). This is useful for event marketing, product launches, and time-sensitive promotions where you want to see the traffic curve as it happens.

Do I need a paid QR generator to get analytics?

Not necessarily. Some platforms (U2L AI included) offer dynamic QR generation with basic scan analytics on free plans, and unlock deeper analytics (unique visitors, referrer detail, longer data retention) on paid tiers. Free static-only generators offer no analytics at any tier. Check the specific plan before committing to a campaign.

How long is scan data retained?

It depends on the platform and plan. Some free tiers keep scan history for 90 days, some paid plans keep it for a year or more, and enterprise tiers keep it indefinitely. Long-running campaigns should confirm the retention window before launch, or export the data monthly to keep a permanent record.

The QR Analytics Baseline

Tracking a QR campaign is a solved problem in 2026. Use dynamic codes, tag the destination URL with clean UTM parameters, generate one code per placement, and check the dashboard weekly. That's it. Everything else is optimization on top of a working baseline.

If you're ready to generate trackable QR codes with a full analytics dashboard behind them, create a free U2L AI account and get your first dynamic QR live in under two minutes. You can also spin up a code without an account at the QR code generator when you need to ship something today.

Ready to try U2L AI?

Free forever plan. No credit card required.

Get Started Free View Pricing