Back to the guides

Business and measurement

How to measure QR code performance in a small business

This article was generated using AI. Publisher: QRelay — Sebastian Kula.

Scans are a starting point. Set a goal, separate placements and see what actually helps customers take the next step.

A QR code on a flyer, table or vehicle should lead to a specific action. Scan totals describe only part of that journey. To assess whether a printed placement helps your business, combine QRelay’s basic measurement with an observation of what customers do after opening the page. You do not need an elaborate report to begin. You need one question, comparable conditions and a record of changes. This guide explains how to start and what a counter cannot tell you.

1. Choose one task and one outcome

For a restaurant, the goal may be easy access to the current menu. For a photographer, it might be viewing a portfolio and sending an enquiry. For a trades business, it could be a call from someone reading the vehicle graphics. Write down the goal before printing and choose a page that makes the task straightforward. A homepage with a dozen links is not always the best destination. Decide how you will recognise the outcome: opening a menu is different from ordering, submitting a form or confirming a booking. Do not treat them as interchangeable.

2. Use separate codes for separate placements

If you put the same code on a business card and a poster, one shared counter cannot tell you which placement produced the visit. Create separate codes with clear names, such as “Window — menu” and “Tables — menu”. They can point to the same address. Separate placements you actually want to compare, within your plan’s code limit. Avoid dozens of variants without a business question behind them. Record when each placement went live: a code displayed all month is not directly comparable with a poster put up on Friday.

3. Read the counter for what it measures

QRelay shows the total recorded requests through a redirect and daily scan summaries. The dashboard history covers 7 days on Free and 30 days on Pro; Pro also supports exporting events to CSV. Daily history depends on the statistics module being available on the hosting setup. A recorded request is not a unique person. Repeat opens, your own tests and automated traffic may affect the counter. It does not confirm a purchase, time spent on the destination page or a complete view of that page’s traffic.

4. Compare similar periods and change one thing

Choose a complete business cycle, such as two consecutive weeks with similar opening hours. Record scans, days on display and important circumstances: a local event, a closure or a larger campaign. If you are testing the caption beside a code, keep its size, placement and destination the same. Changing everything at once makes the result hard to interpret. With small totals, a single day may be a fluctuation, so avoid declaring a winner after a handful of visits. Longer observation and repeating the test are usually more useful than an impressive percentage from a tiny sample.

5. Measure later actions on the destination page

If you have your own website and separately configured analytics, you can add UTM parameters to the destination URL. One naming example is utm_source=window, utm_medium=qr and utm_campaign=autumn_menu. Parameters describe a source and campaign; adding them does not install analytics. Form or booking measurement must be implemented in the external destination service, with its privacy settings and any required consent taken into account. QRelay does not automatically turn scans into a sales report. Use consistent names and never include customer personal data in the parameters.

6. Turn observations into decisions

For illustration only, imagine a poster recorded 40 scans and produced 4 confirmed enquiries through a separately measured form. This is not a QRelay result or a performance promise. Such a record can still help you ask whether the enquiries were useful and the poster’s production cost made sense. Without knowing how many people saw the print, you cannot reliably calculate a scan rate. Without costs and a business outcome, you cannot calculate return on investment. Record missing data honestly instead of filling the gaps with assumptions.

7. Set up a short weekly review

Check the link, inspect the physical sticker and note the counter on the same weekday. With a short dashboard history, regularly recording your observations preserves useful context. If something seems wrong, first check code readability, the connection and the destination page. Then assess the caption and whether the placement makes sense. Measurement should lead to a decision: clarify the message, move the print, simplify the form or keep a setup that works. Collecting an ever larger scan total is not, by itself, a business benefit.

8. Add context by listening to customers

Ask a few people whether they noticed the code, understood what it would open and found what they needed afterwards. This is a short usability conversation, not a representative survey. Record recurring difficulties without identifying individual people. A low scan count may reflect poor visibility rather than a lack of interest in the offer. A high scan count with few enquiries suggests looking at the destination page and whether its content matches the promise made on the printed material.

Sources and further reading

Put it to work in your business

Start with a free account and see how QRelay fits your day-to-day work.