QR Code Analytics: What to Track and How to Measure Real Performance

A QR code without measurement is just a shortcut. A QR code with a measurement plan becomes a channel you can compare, test, and improve.

The good news is that you do not need an expensive platform to get useful numbers. With a bit of planning, even plain static QR codes can tell you which poster, flyer, or package insert actually sends people to your website and what they do once they get there. This guide explains what QR code analytics really measure, the honest limits of static codes, and a practical workflow using UTM parameters and Google Analytics.

What QR Code Analytics Actually Measure

There are two very different things people mean by “QR code analytics”:

• Scan analytics: counting the moment a phone reads the code. This requires the code to point at a server that logs each request before forwarding the visitor. That is how dynamic QR services work.
• Destination analytics: measuring the visits and actions that happen on your website, app, or form after the scan. This works with any QR code, including static ones, as long as you control or can measure the destination.

A static QR code is just an image of your data. Nothing “phones home” when it is scanned. So if your code simply contains https://example.com/menu, the scan itself leaves no trace anywhere except in whatever analytics your destination page already runs.

A Note on MultipleQR

MultipleQR generates static PNG QR codes in your browser. It is free, needs no signup, and does not track scans. The codes encode exactly what you paste, one value per line, and they keep working forever because there is no redirect service in the middle. What MultipleQR is good at is producing many distinct codes quickly, and that is exactly what a destination-analytics setup needs.

The Metrics That Matter

Total visits from QR codes is the first number you will look at, but it should not be the last. A code that gets plenty of visits and no conversions usually points to a weak landing page or a mismatch between the printed promise and what people see.

Focus on:

• Sessions per placement: which physical location or material drives the most visits.
• Conversion rate after the visit: form submissions, purchases, bookings, downloads, or calls.
• Engagement: time on page and whether people continue past the first screen.
• Time patterns: which days and hours bring QR traffic, useful for staffing and timing offers.
• Device mix: QR traffic is almost entirely mobile, so this mostly confirms your page must be fast on phones.

Method 1: UTM Parameters and Google Analytics

UTM parameters are tags you add to the end of a URL. Analytics tools such as Google Analytics read them and attribute the visit to a source, medium, and campaign. Because the tags live inside the URL, they work perfectly inside a static QR code.

A tagged URL looks like this:

https://example.com/spring-sale?utm_source=store_window&utm_medium=qr&utm_campaign=spring_sale_2026

The five standard parameters:

Parameter	Purpose	Example value
utm_source	Where the code lives	store_window, flyer, receipt
utm_medium	The channel type	qr (keep it constant)
utm_campaign	The initiative	spring_sale_2026
utm_content	Variant or creative	poster_a, poster_b
utm_term	Optional extra detail	aisle_4

Step-by-Step Workflow

1. Pick one destination page per campaign and make sure it loads fast on mobile data.
2. Decide your naming rules before creating anything. Use lowercase, underscores instead of spaces, and a fixed utm_medium=qr so all QR traffic is easy to filter.
3. List every placement where a code will appear: each store, each flyer version, each event booth.
4. Build one URL per placement in a spreadsheet. Put the base URL in one column, the placement name in another, and join them with a formula.
5. Paste the finished URLs into MultipleQR, one per line, or upload them as a TXT or CSV file. Each line becomes its own QR code.
6. Download the codes as a ZIP. Files are numbered in the same order as your list, so keep the spreadsheet to know which file goes where.
7. Test every code by scanning it and checking that the visit appears in Google Analytics’ real-time report with the right source.
8. Report weekly by filtering session source/medium for qr and comparing placements side by side.

For example, a coffee shop running one campaign in three locations would paste:

https://example.com/loyalty?utm_source=downtown_counter&utm_medium=qr&utm_campaign=loyalty_2026
https://example.com/loyalty?utm_source=airport_counter&utm_medium=qr&utm_campaign=loyalty_2026
https://example.com/loyalty?utm_source=campus_table&utm_medium=qr&utm_campaign=loyalty_2026

Three lines, three codes, three separate rows in your report. For larger projects, the same approach scales to hundreds of placements, as covered in our bulk QR code generator guide.

Method 2: Unique Short Paths on Your Own Site

Long UTM URLs make denser QR codes, which need to be printed larger to scan reliably. If space is tight, you can create short paths on your own domain, such as example.com/q/window1, that redirect to the full tagged URL. Most website platforms and hosting providers support simple redirect rules.

This has two advantages. The QR code stays small and clean, and your server logs record each request to /q/window1, giving you something close to scan counts. It also lets you change the final destination later by editing the redirect, as long as you keep your domain. Just remember that if the redirect rule is deleted, the printed code breaks.

Method 3: Destination-Side Analytics

Sometimes the destination is not your website. You can still measure:

• Forms: Google Forms and similar tools show response counts. Use one form per placement, or add a hidden or pre-filled field to tell placements apart. See our Google Forms QR code guide.
• Coupons: a unique discount code per placement shows redemptions directly in your point of sale.
• Phone and messaging: a dedicated number or a pre-filled WhatsApp message per campaign makes inquiries attributable.
• App stores: store consoles offer campaign links with their own attribution.

When a Dynamic QR Service Makes Sense

If you need true scan counts, location data by scan, or the ability to change destinations without owning a redirect, a dynamic QR service is the right tool. These platforms put a short link inside the code and log each scan before forwarding the visitor. The trade-offs are usually a subscription, dependence on the provider staying online, and codes that can stop working if the account lapses. Our comparison of dynamic vs static QR codes goes deeper into that decision.

Common Mistakes

• One code everywhere. If every poster, flyer, and package uses the same URL, you cannot tell which one works.
• Inconsistent naming. Store_Window, store-window, and storewindow show up as three different sources.
• Forgetting the label. A code with no call to action gets fewer scans, which makes your comparisons noisy.
• Tagging internal links. Use UTMs only on the URL inside the QR code, never on links within your own site, or you will overwrite the original source.
• Not testing after printing. A code that scans on screen can fail on glossy paper or at small sizes.
• Treating visits as scans. Destination analytics miss scans where the page never loaded or tracking was blocked, so treat the numbers as a reliable comparison rather than an exact count.

Measurement Checklist

• One destination page per campaign, tested on mobile
• Naming convention written down before generating codes
• One unique URL per placement, built in a spreadsheet
• Codes generated in bulk and matched to the spreadsheet order
• Every code scanned and verified in real-time analytics
• Conversions defined in your analytics tool
• A recurring report comparing placements

FAQ

Can I see how many times a MultipleQR code was scanned? No. MultipleQR creates static codes and does not log scans. Measure the visits at the destination with UTM parameters, or point the code at a redirect you control.

Do UTM parameters slow down the scan? No, but they make the URL longer, which makes the code denser. Keep parameter values short or use a short redirect path.

Will the codes stop working? Static codes keep working as long as the URL inside them works. There is no expiring service in between.

How many codes can I create for testing? As many lines as you paste or upload, all free.

Final Takeaway

QR code analytics are really about attribution: knowing which physical touchpoint led to which action. Static codes cannot count scans on their own, but unique tagged URLs per placement give you clean, comparable data in the analytics tools you already use. Build your URL list, generate the codes in one batch with MultipleQR, and let the numbers show you where to put your next print budget. For ideas on where to place them, see our QR code marketing strategies.