Total scans vs. unique scans: what your QR code numbers actually mean

A code shows 400 scans this month. Is that 400 different people finding you, or 60 regulars scanning it seven times each because that’s just how many times they check the specials? The number alone can’t tell you. The two numbers together can.

Total scans counts events. Unique scans counts people.

Total scans is every time the code got scanned, full stop, including the same person five times in one afternoon. Unique scans is the count of distinct scanners, so that same person scanning five times counts once. Neither number is more “correct” than the other. They answer different questions.

Total tells you volume: how much traffic this code is actually handling. Unique tells you reach: how many different people it’s actually reaching. A code can have high total and low unique (a handful of regulars checking back often) or the reverse (lots of one-time scanners, nobody coming back). Both are real outcomes, and they mean different things about what’s actually happening at that printed code.

What repeat scanning actually tells you

If total is a lot higher than unique, people are coming back on purpose. That’s usually a good sign, not a red flag, it means the code earned a second look. A DJ’s code linking to the current setlist gets rescanned by the same fans checking what’s playing next. A restaurant’s specials board gets rechecked by regulars deciding what to order. A high repeat share means the destination is worth returning to, which is the actual goal of a code that updates instead of staying static.

A repeat share near zero isn’t automatically bad either. A code on a one-time event flyer or a single mailer isn’t supposed to get rescanned, most of its scans should be first-timers by design.

Read repeat share next to where the code is placed, not on its own. The number means something different on a menu table tent than it does on a business card.

Why unique counts are approximate, on purpose

Graklink doesn’t use cookies or fingerprinting to identify who scans a code. That’s the exact kind of tracking a QR code’s privacy promise is supposed to avoid, so unique counts are built from one-way visitor codes instead, not a cookie following someone around.

The tradeoff: shared Wi-Fi can blur the number. A table of ten people scanning your menu on the restaurant’s Wi-Fi can look like fewer distinct scanners than it really was, since they may share a hashed network identity. The number is a solid approximation, not an exact headcount, and that’s a fair trade for not tracking anyone individually to get a cleaner one.

Reading the trend, not just the snapshot

A single month’s total or unique count is a snapshot. The more useful number is the trend: is this 30 days up or down from the last 30 days. A code that’s flat for months and then climbs tells you something changed, a new placement, a mention somewhere, a menu update people are curious about. A code trending down might mean the physical placement got covered, moved, or is simply getting less foot traffic than it used to.

What to actually do with these numbers

Look at total and unique together before drawing a conclusion from either alone. High total, low unique: a small group scanning often, probably regulars. High unique, low total: broad reach, low return interest, common for one-time print runs. Both trending up together: the code is reaching more people and they’re worth coming back to, which is the best version of the outcome.

None of this requires guessing. Pro analytics shows total, unique, repeat share, and the 30-day trend on every code, alongside where and when people are actually scanning. Free accounts still get the total count, forever, no time limit on that number either.