Why improving unique versus repeat scans is worth the effort
Unique versus repeat scans split your scan total into first-time scanners and people who have scanned before. The split tells you whether a code is still reaching new people or mainly serving returning visitors.Neither a high unique share nor a high repeat share is good on its own. The right mix depends on whether the code exists to acquire, serve, or retain.
Diagnose before you change anything
Improvement starts with diagnosis, not with redesign. Before changing a code, split unique versus repeat scans by placement, offer type, and time since launch and look for the weakest segment. The weakest segment is where a fix buys the most, because it holds the largest pool of lost value. Also check the steps around unique versus repeat scans: a problem upstream, such as poor placement, can masquerade as a problem with the code itself, and a problem downstream, such as a slow landing page, can waste scans that were earned fairly. Fix the constraint, not the symptom.Write down your diagnosis in one paragraph before you touch anything. State what you observed, which segment is weakest, and what you believe is causing it. This paragraph is your hypothesis, and it keeps the work honest: if the fix does not move the number, the hypothesis was wrong, and you learn something instead of merely changing things.
Levers that move unique versus repeat scans
- Give returning scanners a reason to come back, such as updated content or a new offer. - Open new placements when unique scans flatten but repeat scans stay strong. - Rotate creative so regulars notice the code again instead of tuning it out.Work through the levers in order of expected impact per unit of effort. A lever that costs nothing and affects every scanner beats a lever that costs a print run and affects one placement. For each lever, state the change, the cost, and the segment it should move, then implement only that change. Bundling several changes together feels productive, but it destroys your ability to learn which one worked.
Test the change properly
Unique share = unique scanners divided by total scans, multiplied by 100. Repeat share = 100 minus unique share.Illustrative example numbers, not real-world data: 300 unique scanners out of 400 total scans gives 300 / 400 x 100 = 75% unique and 25% repeat. A loyalty code would reasonably show the opposite pattern, with repeat scans in the majority.
Run the change as a comparison wherever you can: the old version against the new version, on comparable placements, over the same kind of period. Keep everything else stable, and decide in advance how long the test runs and what counts as a win. A test that ends the moment one variant pulls ahead is not a test, it is a reaction. If traffic is too small for a formal test, change one thing, record the before and after numbers, and treat the result as suggestive rather than proven.