A QR image encodes a string, usually a URL. A camera can detect that image without opening the destination, so a camera scan and a recorded link click are not the same event. Plan measurement around the URL request you can actually observe.
Plan before publishing
Create the final mobile-friendly destination, add consistent UTM values for the placement, then decide whether to encode that long URL or a managed short link. A managed link is useful when printed material may outlive the destination.
- Use one placement naming convention.
- Test the printed proof, not only the screen preview.
- Keep a readable fallback URL near important codes.
Build and test the workflow
For a conference poster, use source=conference, medium=qr and campaign=product_demo. Give separate content values to the entrance sign and booth card only when that distinction will change a decision.
Worked example
Generate the static PNG locally, preserve a quiet zone and strong contrast, then test at the expected print size and viewing distance on multiple phones. Open the result and inspect the complete final URL before ordering prints.
Measure the right outcome
DrutoLink can report ordinary click analytics when the QR opens a managed DrutoLink link. The public QR generator does not save a QR asset, count camera detections or provide a separate scan-attribution channel.
Troubleshooting checklist
- Code will not scan: restore contrast and quiet zone.
- Campaign is missing: inspect the decoded final URL.
- Clicks look low: remember camera detections are not link opens.
Product limits and responsible use
Do not put secrets or personal data in the URL. A static image cannot change its encoded destination, and decorative edits, poor contrast, small print, glare or a broken mobile page can make an otherwise valid code unusable.