QR Scan Analytics That Matter: What to Track After the Code Hits Print
Once a QR code is printed, four metrics matter most: scans, unique days, destination changes, and dead codes. Here's how to track each one, read it, and act on it.
Mike · · · 10 min read · 2,117 words

The code is printed. Now what?
Once a QR code is on a poster, a package, or a table tent, you can't change the print. What you can still change is what you learn from it. Good qr code scan analytics won't give you a vanity number. They tell you whether a placement is working, whether it's still working, and whether anyone broke it since launch.
This guide covers the four metrics we think matter most after print: scans, unique days, destination changes, and dead codes. It also covers how to set codes up before print so those numbers mean something, plus a checklist for a weekly review.
First: what can actually be measured
Not every QR code can be tracked, and it helps to be clear about why.
- Static QR codes hold the final URL directly in the pattern. A phone decodes it and goes straight to your site. No QR service sits in between, so there's no redirect log of scans. Your web analytics or server logs can still count requests to that URL, and UTM parameters can attribute the traffic if your analytics is configured for them. Keep in mind these are landing-page requests, not necessarily scans or individual people.
- Dynamic QR codes hold a short redirect URL. Each scan hits the redirect service first, which logs the request and then forwards the visitor to the current destination. That logging step is what makes it possible to track qr code scans at all. It's also why the destination can be changed after printing.
There's a practical rule here. If you need scan data, or you think the destination might change, use a dynamic code. If the code points to something permanent, like a Wi-Fi network, a vCard, or a URL you control and will never move, a static code is simpler and doesn't depend on any service.
The four metrics that matter
1. Scans: volume, not headcount
What it is: how many times the redirect URL was requested, in total and per code.
Why it matters: it's the basic signal that people saw the code, decided it was worth pulling out a phone for, and followed through. If each placement has its own code (more on that below), scans per code let you compare placements directly.
How to read it carefully:
- One person can scan the same code several times, for example because the page loaded slowly or they wanted to come back later.
- Some apps and security tools fetch URLs automatically when a link is shared in a chat or email. That can add requests that aren't real people standing in front of your print.
- When a phone camera shows a URL preview, many camera apps decode the code without fetching the URL until the user taps through. Some scanner apps, messaging apps, and security tools do fetch or check the URL beforehand, though, so previews can also produce logged requests.
So treat scans as a trend and comparison metric, not a count of people. "Placement A gets about twice the scans of Placement B, week after week" is a solid conclusion. "312 people saw our poster" isn't.
2. Unique days: is the placement alive?
What it is: how many calendar days had at least one scan. You can work this out from daily scan counts if your dashboard doesn't show it directly.
Why it matters: total scans are easy to distort. A launch event, a social post showing the code, or one busy weekend can produce a big number that says little about the next three months. Unique days show persistence: whether the code keeps getting scanned while it sits in the world.
Here's a hypothetical comparison:
- Code A: 280 scans, all in the first 4 days, then nothing.
- Code B: 140 scans spread over 50 of the last 60 days.
On totals, Code A wins. As a long-running placement, Code B is clearly healthier. Code A may have been a one-off spike, or the print may have been taken down, covered, or damaged.
Unique days are especially useful for:
- Packaging and product inserts, where scans arrive slowly over a long shelf life
- Fixed signage like store windows, transit, and menus
- Spotting the moment a placement stops working, even when its lifetime total still looks good
3. Destination changes: the audit trail
What it is: a record of every time a dynamic code's destination URL was edited. It should include what changed, when, and ideally who changed it and why.
Why it matters: being able to edit the destination is the main reason to use dynamic codes, but each edit is also an event that affects your analytics. If conversions on the landing page drop on the 14th and someone changed the destination on the 14th, you want to find that out in seconds, not after a week of digging.
Good practice:
- Write down every change in a shared place: date, old URL, new URL, reason. If your tool keeps an edit history, still add the reason, because tools rarely capture it.
- Don't change destinations in the middle of a test. If you're comparing two placements, keep them on the same landing page until the comparison is done.
- Mark changes on your web analytics timeline so whoever reads the landing-page numbers later knows the traffic source changed.
- Limit who can edit. A code printed on 50,000 boxes is production infrastructure. Treat edit access that way.
Frequent changes aren't a problem in themselves. Seasonal menus and rotating promos are normal uses. Undocumented changes are the problem.
4. Dead codes: silent and broken
A dead code is a printed code that no longer does its job. There are two kinds, and you find them in different ways.
Silent codes still work but nobody scans them. You'll see zero scans, or a sudden drop to zero, over a period you define. Common causes:
- The print was removed, covered, faded, or damaged
- The placement changed: a display moved, a mailer finished landing, an event ended
- The code was printed too small or with too little contrast to scan from where people actually stand
Broken codes get scanned but send people somewhere useless:
- The destination returns a 404 or redirects to a generic homepage
- A promo page expired while the print is still out there
- A form, booking link, or file link behind the code was deleted
- The dynamic code itself was deactivated, or the account behind it lapsed
That last one is worth planning for. A dynamic code only works while its redirect service is active. Before you print something with a long life, like packaging, permanent signs, or books, check your plan terms and decide who owns the account in two years.
Set a dead-code threshold before launch. For a busy storefront, three days with no scans might be alarming. For a product insert, three weeks might be normal. Pick a number for each placement type and review against it, so you aren't guessing every time.
Secondary signals worth a glance
Most dynamic QR dashboards show more than the four metrics above. These are useful as context, as long as you know their limits:
- Time of day and day of week: helps you connect scans to footfall, shift patterns, or delivery windows.
- Device or OS: handy for choosing what to test first on the landing page. It's not a reliable demographic.
- Approximate location: usually based on IP address, which makes it coarse. Mobile carriers and VPNs can place a scan in the wrong city. Use it to confirm a regional rollout, not to locate individual stores.
None of these replaces having one code per placement. Placement-level codes answer most "where is this coming from?" questions more reliably than location data does.
How to set up tracking before print
Clean analytics after print depend on decisions made before it. Work through these steps for each campaign.
- Give every placement its own code. Poster, flyer, and packaging each get one. If a placement has variants, like two poster designs or three cities, give each variant its own code too. Analytics can't split one code into placements afterward.
- Name codes consistently. For example:
spring26_poster_station-northorpkg_sku1042_insert. You'll filter and sort by these names for months. - Add UTM parameters to the destination URL. Use
utm_source=qr, plusutm_mediumandutm_campaignthat match the code name. Your web analytics can then follow QR traffic past the scan to signups, purchases, or bookings. - Record the launch details: print date, quantity, location, and expected lifespan. A scan count only means something next to how many prints went out and for how long.
- Test the printed proof at final size. Scan it from the distance and angle people will actually use, on more than one phone, in the lighting of the real location.
- Set a dead-code threshold for each placement type, as described above.
- Decide who may edit destinations, and where changes get written down.
These steps are the difference between a scan dashboard and usable qr campaign metrics.
Decision table: what the pattern is telling you
| Pattern you see | Likely meaning | What to do |
|---|---|---|
| High scans, few unique days | Short-lived spike (event, social share, launch) | Don't plan long-term placements around it; look at steady-state weeks |
| Steady scans, many unique days | Healthy long-running placement | Leave it alone; consider copying the placement elsewhere |
| Scans dropped to zero suddenly | Print removed, covered, or placement ended | Check the physical location; refresh or retire the code |
| Scans normal, landing conversions dropped | Destination problem or recent edit | Check the destination-change log; test the page on mobile |
| Very low scans from launch day | Visibility, size, contrast, or call-to-action issue | Check the print at real viewing distance; rewrite the "why scan" line |
| Scans keep coming after a promo ended | Long-lived print outlasting the offer | Redirect to an evergreen page instead of a dead one |
| One variant clearly beats another over weeks | Real placement or design difference | Use the winner in the next print run |
Weekly review checklist
Fifteen minutes a week is usually enough for a mid-sized campaign:
- [ ] Check scans per code against last week. Flag any change of more than about 50% either way.
- [ ] Count unique days in the last 7 and 30 days for each long-running placement.
- [ ] List codes past their dead-code threshold and assign someone to check each one physically or online.
- [ ] Open every active destination on a phone. Confirm it loads, isn't a 404, and the offer is current.
- [ ] Review destination changes made this week. Each should have a logged reason.
- [ ] Compare QR-tagged sessions in web analytics with scan counts. Some gap is normal: automated fetches, repeat requests, people leaving before the page loads, and analytics blocking or consent settings can all cause one. A large or sudden gap is a reason to investigate, not proof of a redirect or page-load fault.
- [ ] Retire or redirect codes for campaigns that have ended but still have print out there.
Common mistakes to avoid
- Reusing one code across many placements. It's convenient at print time and leaves you unable to tell placements apart afterward.
- Reporting scans as people. Use "scans," not "visitors" or "reach," unless you've deduplicated with your web analytics.
- Letting promo pages expire under printed codes. Point expired campaigns to a useful evergreen page.
- Printing long-life codes without an ownership plan. Someone has to keep the dynamic code active for as long as the print exists.
- Editing destinations without telling anyone. Every unlogged change makes your history harder to trust.
When you manage codes for other people
Agencies, SaaS platforms, and print services that create codes for their own customers have the same four metrics multiplied across many accounts. That makes naming conventions and edit permissions even more important. If you need to offer dynamic qr analytics under your own brand, Max QR's white label program uses prepaid credits, your own branding and pricing, and a private API key. Contact us to get it set up.
Try it on Max QR
You can create static codes for free without an account, with custom colors, logos, and PNG or SVG export, at getmaxqr.com. To track scans after print, you need dynamic codes. Pro adds dynamic codes, destination editing, scan analytics, and saved projects. See the pricing page for details, or create an account and open your dashboard to make your first trackable code.
Generating codes in bulk or through code? The docs cover CSV bulk creation and the developer API on Business. The blog has more guides on print sizing and campaign setup.
Try it on your campaign
Design a QR code in the browser — the same workflow we write about.


