Why the print cannot count anything
When a phone scans a code, it decodes a string of characters and opens it. The card has no connection to anything, no identifier and no way to know it was used. Everything you learn about a scan has to be measured at the destination.
That is why claims about tracked printed codes always turn out to describe a redirect service sitting between the code and the real page. There is nothing wrong with that approach, but it is a separate service you choose and pay for, and it is worth understanding what it actually does before assuming your printer provides it.
Method one: a unique landing page
The simplest reliable method. Point the card code at a page that exists only for that purpose, such as a short path on your own site, and read the page view count in your normal web analytics.
It works because the page has no other traffic source. Nobody types it, no menu links to it, and it is not in your sitemap navigation. Any visit is a scan or something very close to one.
The cost is that you now maintain a page. Keep it genuinely useful: your contact details, a booking link, a short description of what you do, and a way to save your details. A page that exists only to be counted feels like one, and visitors notice.
Method two: a redirect path you control
If you do not want a separate page, use a distinct path on your own domain that redirects to the real destination. Your server or hosting platform logs the request, so you can count the redirects without changing the destination page at all.
This has a second advantage that matters more than counting: you can change where the code goes after the cards are printed. If the campaign page changes, you repoint the redirect rather than reprinting 500 cards. Treat that as the main reason to use a redirect and counting as a bonus.
Keep the path short and readable, because a short path also produces a smaller, more reliable code.
Method three: campaign parameters on the link
Add parameters to the destination URL so your analytics separates that traffic from everything else. The naming system in the guide to UTM links for print campaigns keeps the values consistent across pieces, which is what makes the reports readable a year later.
The trade off is length. Parameters make the encoded string longer, which raises the module count and shrinks each module at the same printed size. On a business card that can cost you the reliability you were trying to measure. If you need parameters, put them on the redirect target rather than in the printed code, so the code stays short and the parameters are added by the redirect.
Method four: ask
Unglamorous and consistently underrated. Add one question to your inquiry form or your first conversation: how did you find us. Categories, not free text: card, website, referral, event, search.
This catches something no digital method can. A person who reads your card, does not scan it, and searches your name later is a result of the card, and every scan based method records that as organic search. If you only measure scans, you will systematically undervalue print.
How do you compare the methods?
| Method | What it counts | Effort | Weakness |
|---|---|---|---|
| Unique landing page | Visits to a page with one source | Low | Needs a page worth visiting |
| Redirect path | Requests to a path you control | Medium | Needs server or platform access |
| Campaign parameters | Sessions tagged in analytics | Low | Lengthens the code |
| Asking | Self reported source | Very low | Depends on people answering |
Most small businesses do best with a redirect path plus the question. The redirect gives you a number and the ability to change the destination; the question gives you the context the number is missing.
What should you actually measure?
Scans are an activity, not a result. Counting them is only useful if you also count what happened next.
- Scans or page visits, as the top of the funnel.
- Actions taken on the page: contact saved, form submitted, call started, booking made.
- Enquiries that name the card as the source.
- Cards handed out during the period, so you can express scans as a rate.
That last number is the one people skip, and without it the scan count means nothing. Two hundred scans from 2,000 cards is a very different result from 200 scans from 250 cards.
What is the measurement checklist?
- Accept that the printed code itself records nothing.
- Point the code at a unique path or page on your own domain.
- Prefer a redirect so you can change the destination without reprinting.
- Keep parameters off the printed code and add them at the redirect.
- Add a how did you find us question with fixed categories.
- Count cards handed out so scans can be expressed as a rate.
- Review the numbers per batch of cards, not per week.
Frequently asked questions
Can you tell me how many people scanned my business card QR code?
No. The printed code is a static image of a web address with no connection back to us, and we do not provide dynamic codes or a scan analytics service. Anything you learn about scans has to be measured at the destination, using your own website analytics, server logs or a redirect service you control.
What is the easiest way to count QR scans from print?
Point the code at a path that exists only for that purpose on your own domain, then read the visit count in your normal analytics. Because nothing else links to that path, almost every visit is a scan. Adding a redirect at that path also lets you change the destination later without reprinting.
Should I put UTM parameters directly in a printed QR code?
Usually not on something as small as a business card. Parameters lengthen the encoded string, which adds modules and shrinks each one at the same printed size, making the code less reliable. Encode a short path instead and let the redirect add the parameters on the way to the destination.
Is a low scan count a sign the card is not working?
Not on its own. Many people read a card, keep it and search your name days later, which every scan based method records as search traffic. Ask new inquiries how they found you, and compare scans against the number of cards actually handed out rather than looking at a raw count.
Sources & specification notes
The references below support the relevant technical or product details in this guide. Examples and checklists are not claims of practical testing or universal supplier requirements. Confirm the current specifications for your chosen product before production.
- FTC Consumer Alert: Scammers hide harmful links in QR codes ↗
Advises checking that a QR destination looks like a recognizable URL, which is a reason to use a short readable path on your own domain rather than an opaque third party shortener.
- DENSO WAVE: How to create a QR Code, margin and cell size ↗
Shows how encoded data length drives symbol version and module size, supporting the advice to keep printed links short.
