Scan analytics

Total scans and unique scans

Total counts every scan event. Unique counts a device once within the aggregation window. One person scanning three times adds three to the first number and one to the second, which is why the two never match.

Reviewed August 20, 2026

Steps

1. Use total when you care about interaction volume — how often the code is being used.
2. Use unique when you care about reach — roughly how many people, not how many taps.
3. Compare like with like: the same code, the same period, the same time zone.
4. Expect your own team’s testing to be in the numbers unless you scanned before publishing.

How to check it worked

Scan a published code twice from one phone and once from another, then wait for aggregation. Total should rise by three and unique by two.

What usually goes wrong

• Reading unique scans as a headcount — it is devices, within a window.
• Comparing a week against a month.
• Counting the print run’s own QA scans as customer interest.