How to Track QR Code Scans: A Practical Analytics Guide

A QR code without tracking is a flyer you throw over a wall: maybe somebody catches it, maybe not — you'll never know. Tracking turns the same square of pixels into a measurable channel with per-location, per-day, per-device numbers. Here's how scan tracking works, how to set it up in a minute, and which metrics are actually worth your attention.

How scan tracking works (no magic involved)

Tracking requires a dynamic QR code. Instead of encoding your destination directly, the code carries a short redirect URL. Each scan hits that URL first; the server records the event — timestamp, device type, approximate location by country — and instantly forwards the visitor to the real destination. The detour takes milliseconds and is invisible to the person scanning.

Two consequences worth understanding:

• Static codes cannot be tracked. The scan resolves entirely on the phone; no server is involved, so there is nothing to count. If you printed a static code and want numbers, the honest answer is: reprint as dynamic. (Full comparison: dynamic vs static.)
• No app, no pixel, no cookie banner dance. Counting happens server-side on the redirect, not by scripts on your landing page — it works even if the destination is a PDF or someone else's website.

Set it up in three steps

1. Create a dynamic QR code — pick any type in the generator catalog: URL, menu, PDF, vCard, app link. Dynamic mode with tracking is on by default for saved codes.
2. Deploy it — print, embed, or share. If you run several placements (poster vs table tent vs packaging), create one code per placement; that's what makes per-location comparison possible.
3. Open the dashboard — the analytics view shows scans per code as they happen. Numbers update in real time; no reports to schedule, nothing to install.

The metrics that matter (and what to do with them)

Total scans and scans over time. The baseline. A launch-day spike that dies in a week means the placement works but the offer doesn't hold attention — or the reverse.

Device breakdown (iOS vs Android). Not trivia: it should shape the destination. An audience that is 80% Android and being sent to an App Store link is a leak. For app campaigns, use an app-download QR that routes each platform to its own store.

Country breakdown. Catches surprises — codes shared beyond the printed medium, or a tourist-heavy location that justifies an English menu.

Peak days and hours. If the lunch crowd scans your menu at 12:40, that's when the daily special should already be online, not at 15:00.

Per-code comparison. The most underrated practice: one code per placement, then compare. Two poster locations, same design, 340 scans vs 12 — now you know where the next poster goes.

Beyond counting: what a tracked redirect enables

Because every scan passes through a redirect you control, tracking is only the start:

• A/B destinations — split traffic between two landing pages and keep the winner.
• UTM tags — scans arrive in your web analytics correctly attributed to the physical campaign.
• Lead capture — show a short form before the redirect when a contact is worth more than a click.
• Bio pages — for link-in-bio codes, click-through on each individual link is tracked too (more on bio pages).

Privacy, briefly

Scan analytics is aggregate campaign data: device class, country, time. It's the same signal any web server sees on any visit — no scan requires a login, and nobody has to install anything. Keep your landing pages honest and your privacy policy current, and QR tracking adds no new obligations in practice.

Start measuring

The difference between "we printed QR codes" and "we know Tuesday's poster in the north entrance outperforms the lobby 4:1" is one checkbox at creation time. Create a trackable QR code — analytics are included in the free tier, with limits listed on the pricing page.