QR codes and campaigns
QR code campaign checklist: destination, readability and measurement
Plan a QR code that remains scannable, opens a trustworthy destination and uses campaign parameters without damaging the URL.
In short
A QR image is only the visible entry point. Success depends on the destination URL, physical size, contrast, error correction, surrounding quiet zone, mobile page and measurement plan. Build the destination first, keep the payload concise and test the printed artifact in realistic conditions.
- Publish and test the destination before generating the code.
- Prefer a short trustworthy HTTPS URL over a dense payload.
- Preserve contrast and the quiet zone around the symbol.
- Test multiple devices, distances, lighting and print materials.
- Use consistent UTM names and avoid personal data in parameters.
1. Define the action and destination
Decide what should happen after the scan: open a page, save a contact, join Wi-Fi or display text. For campaigns, a normal HTTPS page is usually easier to update, measure and explain than embedding a large amount of content directly.
The destination must be live, mobile-friendly and recognizable. Avoid open redirects, unexpected downloads and shortened links that hide ownership. State the destination or purpose near the printed code so users have context and an alternative.
- One clear action selected
- HTTPS destination returns useful content
- Mobile layout tested
- Visible fallback URL or instruction provided
2. Keep the payload efficient
More data creates a denser symbol with smaller modules. Remove unnecessary query parameters and use a concise canonical URL. Do not embed access tokens, personal details or secrets; anyone can photograph and decode the code.
Choose an error-correction level appropriate to the environment. Higher correction can tolerate more damage but increases symbol density. A logo placed over the code consumes that tolerance and should never cover positioning patterns.
3. Design for scanning, not decoration
Use strong contrast, a clear light background and an uninterrupted quiet zone. Avoid stretching, perspective distortion, glossy glare and low-resolution screenshots. Export a vector format for print when the workflow supports it.
Size depends on viewing distance and camera conditions. Print a proof at final dimensions rather than judging a large screen preview. Keep other visual elements far enough away that the scanner can isolate the symbol.
- Dark modules on a light background
- Quiet zone preserved on every side
- No crop or distortion
- Final-size proof printed or displayed
4. Add campaign parameters consistently
UTM parameters help analytics group traffic by source, medium and campaign. Define a naming convention before creating variants; inconsistent capitalization and spelling split reports into separate rows.
Do not put names, email addresses or sensitive audience labels in the URL. Parameters are visible in the browser, logs and shared links. Keep a private mapping between artwork/version and the non-sensitive campaign name.
5. Test the complete artifact
Scan with different phone platforms and camera apps, from expected distance, under bright and dim light, and after the code is placed on the real material. Confirm the browser shows the intended hostname before continuing.
Follow the final page through redirects and test the main action. Keep the source artwork, destination and campaign convention documented so a future reprint does not point at an obsolete or unsafe page.
Next step
Check your own case
Frequently asked questions
Should I use the highest error correction?
Not automatically. It improves damage tolerance but increases density. Choose it with physical conditions and payload size in mind.
Can I change a static QR destination later?
The encoded payload cannot change. You can control a URL you own, but redirects should remain transparent, secure and maintained.
Are UTM parameters private?
No. They are visible in the URL and may appear in logs, screenshots and shared links. Never include personal or secret data.
Why does a code scan on screen but fail in print?
Print size, contrast, material, glare, cropping, resolution or an insufficient quiet zone can reduce recognition.
Primary sources and reference
Sources consulted during editorial review. External links open the organization responsible for the standard or guidance.