Skip to content
Business & Regional

How to Measure QR Scan Rate

Codexengr, QR Systems Engineer
Published 2027-10-28 (Updated 2026-10-05)
5 min read
Peer Reviewed & Fact Checked

What scan rate tells you

Scan rate is the share of people who see a QR code and actually scan it. It connects the physical world, where the code is displayed, to the digital world, where the destination lives.

A code nobody scans is not a design failure alone. It may be in the wrong place, too small, or paired with a promise nobody wants.

How to compute scan rate

Scan rate = scans divided by exposures, multiplied by 100.

Illustrative example numbers, not real-world data: 400 scans from 5,000 exposures gives 400 / 5,000 x 100 = 8%. If exposures rise to 6,000 with the same 400 scans, the rate falls to about 6.7%, which shows why the denominator matters as much as the numerator.

How to collect the data

Count scans from your redirect or analytics tool, and estimate exposures from foot traffic, print run size, or impressions for digital placements. Record both numbers for the same dates and the same placements, or the ratio is meaningless.

Keep the raw counts, not just the final percentage. Raw counts let you recompute the metric if you later fix the definition, and they make it possible to spot a denominator problem, such as a week where exposures were estimated instead of counted. Store the counts in one place with the date range, the placements included, and the name of the person who pulled them. That small discipline turns a spreadsheet into an audit trail.

Reading the result

Never judge scan rate as a single number. Break it down by placement, time of day, creative design, and audience type. A campaign that looks average overall may be strong in one segment and weak in another, and the fix is completely different in each case. Compare the same placement against its own past, and compare different placements only when their audiences and contexts are genuinely similar. A short trend over four or more comparable periods is worth far more than a single snapshot, because it separates a real shift from weekly noise.

Also check the relationship between scan rate and the metrics around it. If scans rise while conversions fall, the new scanners may be less interested visitors, or the landing page may have changed. If cost rises while scan rate stays flat, you are paying more for the same outcome. Metrics make sense in groups, not in isolation, and the habit of reading two or three together prevents most misreadings.

Putting this into practice

Start with one code and one placement. Define scan rate in one sentence, collect the two numbers it needs for two full weeks, and compute the result by hand once so you trust the pipeline. Then set up the same measurement for your other placements, using identical definitions and identical date ranges. When the numbers arrive, write down the one action they suggest, the owner of that action, and the date you will recheck. Measurement without a decision attached is bookkeeping, and bookkeeping does not improve campaigns.

Common mistakes to avoid

- Guessing exposures instead of measuring or estimating them consistently. - Counting test scans by your own team as if they were customer scans. - Judging a result after two days and changing a working placement. - Comparing placements with different audiences as if they were equal. - Reporting a percentage without the raw counts behind it.

Quick checklist

- Define scan rate in one sentence and keep the definition stable. - Collect both sides of the ratio for the same period and placements. - Segment by placement, time of day, creative design, and audience type. - Compare against your own past before judging the number. - Record the raw counts, date range, and method with every reading. - Attach one decision, one owner, and one recheck date to each report.

Related tools and guides

- Model the numbers before you commit with the [QR analytics simulator](/qr-analytics-simulator), which shows every formula behind the projection. - Plan goals, placements, quantities, and QA with the [QR campaign planner](/qr-campaign-planner) before the first print run. - Tag every destination consistently with the [UTM builder](/utm-builder) so each scan can be traced to its placement. - Match printed size to viewing distance with the [QR size calculator](/qr-size-calculator) before you approve artwork. - Test every code in the real location with the [QR scanner](/qr-scanner) on more than one phone. - Check proofs under real conditions with the [printed QR tester](/printed-qr-tester) before a full run. - The [blog](/blog) collects more guides on sizing, printing, security, and measurement for QR codes.

Frequently Asked Questions

What data do I need to measure scan rate?

You need both sides of the ratio: the count of the event, such as scans, and the base it is measured against, such as exposures. Without the base, the count cannot be compared across placements or periods. Record the date range and the exact definition you used, so a later reading is comparable.

How often should I check scan rate?

Check it on a fixed cadence that matches the campaign, such as weekly for active campaigns and monthly for always-on codes. More frequent checks help during a launch, when problems are cheapest to fix. Avoid reacting to a single day of data, since daily numbers swing for reasons that have nothing to do with quality.

Why does scan rate look different across placements?

Placements differ in audience, dwell time, lighting, and intent, so the same code can perform very differently in two spots. Segment the numbers by placement before judging them. A placement that looks weak in aggregate may be strong once you compare it only with similar placements.

Ready to generate high-precision QR codes?

Test your designs in real-time with our 100% client-side QR studio suite. Zero tracking, instant vector downloads.

Open QR Code Studio