1. The Density Problem
A full UTM string such as utm_source, utm_medium, and utm_campaign can add 60 or more characters. That increases the QR version and shrinks modules, making scanning harder at the planned print size. Our [QR size calculator](/qr-size-calculator) shows how payload length affects symbol density.
2. A Cleaner Pattern
1. Give each placement a short path on your own site, e.g. example.com/m1 for the lobby poster—use our [UTM builder](/utm-builder) to plan your tracking structure.
2. Have your web server redirect that path to the long UTM URL.
3. Analytics then attributes the visit correctly while the printed code stays small.
4. Generate the short-URL code with our [URL QR code generator](/url-qr-code-generator).
3. Naming Conventions
Use utm_medium=qr consistently, lowercase values, and one utm_campaign per print run. Use a different path per location so you can compare placements. Before printing, verify scan quality with our [printed QR tester](/printed-qr-tester) and review [placement guidelines](/qr-placement-guide) for optimal results.
4. Trade-off
A redirect you control is still a redirect: if you lose the domain or break the path, printed codes fail. Keep the mapping documented. Consider using our [bulk generator](/bulk-generator) if you need many trackable codes for different locations.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
