How to Track QR Code Scans (Beginner's Guide)

You printed a QR code, put it on the counter, and now the obvious question: is anyone actually scanning it? Out of the box, the answer is unknowable — a standard QR code sends phones straight to a destination and leaves no trace. Tracking requires one small change to how the code is built. This guide covers that change, the options for making it, and what to do with the numbers.

Why your current QR code probably can't be tracked

A QR code is just a URL rendered as squares. If the URL encoded is your final destination (your menu, your Google review form), the customer's phone goes directly there — no counter in the middle, nothing logged. This is a static code, and no tool can retroactively add tracking to it.

A dynamic code encodes a short redirect URL instead: scan → short link (logged) → destination. That indirection is the entire mechanism. Every tracked QR system, free or paid, works this way — and it's the same principle behind why review links should be shortened through your own layer.

Three ways to set it up

Option 1: A URL shortener (free, basic)

Create a short link in any reputable shortener (Bitly and friends), generate a QR from the short link, print. The shortener's dashboard counts clicks — which, for a QR code, are scans.

You get totals and rough timing; you won't get much more on free tiers, and destinations may be limited or ad-wrapped on some services. Fine for testing whether a placement works at all.

Option 2: UTM tags + Google Analytics (free, DIY)

If the destination is a page you own, append UTM parameters (?utm_source=qr&utm_medium=counter-plate) and build the QR from that tagged URL. GA then reports those visits under the campaign.

Powerful, but with real caveats: it only works for your pages (you can't UTM Google's review form), it counts page loads rather than scans, and each variant needs manual tag discipline. Best for menu/booking destinations when you already live in Analytics.

Option 3: A purpose-built platform (paid, complete)

QR/links platforms combine the redirect layer, the analytics dashboard, and — the underrated part — editable destinations: repoint the printed code any time without reprinting. Tools built for hospitality (the category we compared in our Linktree-alternative guide) add the venue-shaped features: review deep-links, multi-destination landing pages, per-card tracking.

One code or many? (Many.)

The single most useful trick in QR tracking: give every placement its own code. Counter plate, table cards, window poster, receipt footer, takeaway packaging — each gets its own short link to the same destination. Now the dashboard doesn't just say "63 scans"; it says the counter outperforms the window five to one, which tells you where the next card goes.

Reading the numbers

The metrics worth your attention (the full breakdown is in our QR code analytics guide):

• Scans over time — is the code alive, and trending up?
• Scans by day/hour — when are engaged customers in the building?
• Per-placement comparison — which surfaces earn their spot?
• Scan-to-outcome conversion — scans against reviews gained, menu views, follows. Scans are the means; this is the end.

And the two classic traps: judging a placement in its first quiet week (give it a month), and celebrating scan totals while the destination page quietly fails to convert (test the full journey monthly, on both iPhone and Android).

Quick answers

Can I track scans without changing the printed code?

Only if the printed code already points at a redirect you control (dynamic) or a page you can add analytics to. If it encodes a third-party destination directly — reprint, properly this time.

Do tracked QR codes collect personal data?

The redirect logs a scan event — time, coarse device type — not identity. No app, no cookies required on the customer's phone. It's counting, not surveillance.

What's a good scan rate for a café?

A visible, well-placed counter code in a busy venue commonly sees scans from 5–15% of transactions when paired with a verbal mention. Below that, move the code or add the mention before blaming the tech.