How to measure a QR campaign from printed code to useful action
Distinguish QR redirect requests, page arrivals, and completed actions while comparing placements fairly.
The useful takeaway
Give each meaningful placement its own link identity and count outcomes after the scan.
A QR code connects a physical placement with a digital destination. That creates a useful measurement opportunity, but it does not make every request a person or every scan a successful visit. A phone can recognize a code without opening it, and a redirect request does not establish that the final page finished loading.
Design the campaign around the task: view a menu, request an estimate, register for an event, or access instructions. Then decide which observations you can collect at the redirect, landing page, and destination. Keep those stages distinct so the report shows progress instead of an impressive but ambiguous scan total.
Assign identities to placements you can act on
Create separate campaign paths for meaningful physical placements, such as front-counter cards and event posters. Do not generate a unique identifier for every person holding a flyer. The useful comparison is usually where and how the code was presented, not who privately encountered it.
Keep a register connecting each path to the artwork, print batch, location, owner, and publication date. If a code appears on packaging distributed for months, record that longer lifespan. A future traffic spike may come from old stock rather than the campaign currently on your calendar. The physical material remains part of the reporting context after the design file is archived.
Check scanning before measuring performance
Use the actual printed proof at the intended size and in realistic lighting. The code's surrounding clear area matters: DENSO WAVE documents a four-module quiet zone. Keep the destination readable as a short fallback URL when practical, so people have another route if scanning fails.
A tracking system cannot reveal people who tried unsuccessfully to recognize a code. That means a low arrival count could reflect poor placement, weak motivation, or a print problem. Test the code at the actual viewing distance and on multiple ordinary phones before drawing conclusions about demand. A clean digital preview is not enough evidence for a printed campaign.
Connect the code to a campaign label
Use campaign parameters on the destination URL when your analytics supports them, with source describing the physical placement and campaign describing the initiative. Google's URL-builder documentation explains the mechanism. Keep labels broad and nonpersonal, and verify that any redirect preserves the intended values.
A short URL can make the encoded payload simpler and let you manage the destination later, depending on the service. That also introduces a dependency. Document who controls the redirect and what happens if a subscription ends. MDN's redirect guide explains the extra request involved; minimize unnecessary chains before the landing page.
Read an illustrative placement comparison
Imagine an illustrative café campaign with 200 counter cards and two window posters. The counter path records 60 landing sessions and 12 loyalty registrations; the poster path records 18 landing sessions and three registrations. These are observed outcomes by tagged route, not proof that the card design is intrinsically better.
The exposure opportunities differ. Cards may be handed directly to customers while posters are seen from a distance by passersby. Record the placement period and distribution method alongside counts. If you know how many cards were actually distributed, report that separately from how many were printed. Unused stock should not become an invented audience denominator.
Inspect the gap after arrival
A code can scan perfectly and still lead to a disappointing page. Check whether the first screen repeats the promise printed beside the code. A sign saying View today's menu should not open an unrelated homepage that requires another search. Measure the promised action and confirm that the destination is available on mobile connections.
If a form or booking tool is involved, verify its completion record in the authoritative system. Keep test scans and staff demonstrations out of campaign reporting where possible. Allow for privacy settings and incomplete collection rather than attempting to bypass them. A report with known coverage limits is more trustworthy than a claim that every physical interaction has been captured.
Plan the final report before printing
Write the decision you want the report to support: whether to reprint, move the sign, revise the offer, or retire a placement. Include production costs, distribution effort, qualified outcomes, and unresolved measurement gaps. A high scan count with no useful action may call for a destination repair rather than more printing.
After the campaign, preserve an honest destination for material still circulating. Explain that an event has ended and offer a relevant next step, instead of silently routing old codes to an unrelated offer. This protects the visitor's expectation and keeps later traffic interpretable when someone scans a card found months after launch.
Sources & further reading
References for the principles and technical details in this guide.
- DENSO WAVE: QR code area and quiet zone
- Google Analytics: Campaign URL parameters
- MDN: HTTP redirections
Found something that needs correcting? Send us a correction.