Dynamic QR codes give marketing teams a practical way to track scans and change a campaign destination without reprinting the code. This guide explains how to set up QR code UTM tracking, compare static and dynamic QR codes, validate redirects, report on performance, and establish a recurring review process for packaging, events, retail displays, and direct mail.
Overview
A QR code is only one part of a campaign link. The printed or displayed pattern sends a device to a URL, while the redirect, destination page, campaign parameters, and analytics setup determine what you can learn afterward.
A static QR code stores its destination directly in the code. If the destination changes, the code normally needs to be replaced everywhere it appears. A dynamic QR code points to a redirect managed by a QR platform or link management system. You can usually update the final destination while leaving the printed code unchanged, subject to the platform's features and the redirect remaining active.
| Consideration | Static QR code | Dynamic QR code |
|---|---|---|
| Destination changes | Usually require a new code and reprint | Can typically be made at the redirect level |
| Campaign tracking | Requires a trackable destination URL and separate analytics | Often includes scan and redirect reporting, depending on the tool |
| Best fit | Permanent, simple destinations with limited reporting needs | Campaigns that may change, need reporting, or run across print channels |
| Operational risk | Less dependence on a redirect service, but less flexibility | Requires active ownership, monitoring, and a maintained redirect |
For a trackable campaign, use a QR code generator with analytics or a link management system that gives the code a stable redirect URL. Then add campaign parameters to the destination URL. The QR platform may report scans or redirects, while your website analytics can report sessions, engagement, and conversions. Treat these as related but separate measurement layers.
Before printing, also test the code on the actual material and at the intended viewing distance. The QR Code Print Quality Guide covers size, contrast, error correction, and scan testing.
What to track
1. Use a consistent campaign URL
Start with the page a visitor should reach after scanning. Add UTM parameters that identify the QR placement without relying on memory or manual interpretation. A practical template is:
https://example.com/offer?utm_source=qr&utm_medium=print&utm_campaign=spring_launch&utm_content=package_front
Adjust the values to match your existing naming convention. For example, packaging might use utm_source=qr, utm_medium=packaging, and a content value such as box_front. A trade-show badge could use utm_medium=event and utm_content=badge. The important principle is consistency: the same placement should receive the same parameter pattern across reports.
Use a UTM tracking workflow to document capitalization, separators, campaign names, and required fields. If multiple advertising or social platforms are involved, compare their parameter conventions with the UTM Parameters by Ad Platform guide.
2. Record the QR code's operational details
Maintain a simple inventory for every code. Include:
- A human-readable code name and owner.
- The redirect URL or short link encoded in the QR code.
- The current final destination.
- The campaign, placement, launch date, and planned end date.
- The UTM values used in the destination URL.
- Where the code appears, such as a package, poster, shelf display, or mailer.
- Whether the destination is editable and how access is controlled.
3. Separate scans from outcomes
A QR analytics dashboard may show scans, redirects, device categories, approximate locations, timestamps, or repeated activity. Website analytics may show sessions, landing-page engagement, form submissions, purchases, or other conversions. These measures answer different questions:
- Scans or redirects: Did the code receive activity?
- Sessions: Did the visit reach the website analytics system?
- Engagement: Did visitors continue beyond the landing page?
- Conversions: Did the campaign produce the defined business action?
Do not assume that every scan becomes a recorded session or that every conversion can be credited exclusively to the QR code. Privacy controls, blocked scripts, repeated scans, offline viewing, redirects, and later visits can all affect attribution.
Cadence and checkpoints
A QR campaign needs checks before launch, immediately after launch, and throughout its active life. Use this workflow as a repeatable checklist.
Before printing or publishing
- Confirm the redirect opens the intended destination over a mobile connection.
- Check that the final URL contains the correct UTM parameters and uses the approved spelling and case.
- Test the QR code from the final physical design, not only from a screen preview.
- Verify the landing page works on common mobile screen sizes and does not require an unnecessary sign-in.
- Record the code, destination, owner, placement, and launch date in the campaign inventory.
- Define the conversion event and reporting owner before launch.
At launch and during the first review
Test one live item from every placement type. A package, event poster, retail display, and direct-mail card may have different lighting, angles, sizes, and scan conditions. Confirm that scans appear in the QR dashboard and that visits arrive in website analytics with the expected source, medium, campaign, and content values.
For technical campaigns or app destinations, test fallback behavior as well. The Deep Link Testing Guide can help when a QR scan should open an app for some visitors and a web page for others.
Monthly or quarterly review
For active campaigns, review performance at a regular monthly cadence. For short events or high-volume campaigns, review more often. Export or record:
- Total scans or redirects and the reporting period.
- Trend by day or week, where available.
- Device category and operating-system patterns.
- Approximate location data, interpreted cautiously.
- Landing-page sessions, engagement, and conversions.
- Error responses, inactive links, and unexpected destination changes.
- Results by placement, creative, or physical distribution channel.
Keep the export with the campaign record. This makes it easier to compare periods without relying on a dashboard's current configuration.
How to interpret changes
A rise or fall in scans is a signal to investigate, not an explanation by itself. Compare the result with distribution volume, campaign timing, placement visibility, and any change to the offer or landing page.
If scans fall suddenly across every placement, first test the redirect and inspect the code's active status. Confirm that the domain resolves, the destination returns the expected response, and no redirect rule or campaign setting has changed. If only one placement declines, examine its physical condition, visibility, lighting, distance, and audience exposure.
If scans are stable but sessions or conversions decline, inspect the destination page, mobile experience, load behavior, offer availability, and analytics tagging. If sessions increase without corresponding conversions, the campaign may be attracting curiosity without matching visitor intent, or the conversion event may be misconfigured.
Device and location data can help identify broad patterns, but avoid treating them as precise individual-level facts. QR analytics may use inferred or approximate information, and privacy settings can limit what is available. Report the level of certainty supported by the data.
How to change a QR destination without reprinting
When using a dynamic QR code, update the redirect's final destination rather than changing the encoded QR value. Before saving the change:
- Confirm the new page is live and appropriate for mobile visitors.
- Preserve the campaign's required UTM parameters unless the reporting plan intentionally changes.
- Check whether the new destination needs a different language, region, offer, or app fallback.
- Test the live QR code from the printed asset and from a second device.
- Record the previous destination, new destination, timestamp, reason, and approver.
- Schedule a follow-up check to confirm the redirect remains correct.
Do not point an old printed code to an unrelated destination without documenting the change. Visitors may scan the code expecting the original offer, and historic results become harder to explain. For broader redirect controls, see the Short Link Lifecycle Management guide.
When to revisit
Revisit this workflow before every new print run, destination update, campaign launch, and monthly performance review. Perform a deeper audit quarterly or whenever ownership, analytics configuration, domains, or privacy settings change.
Use these channel-specific checks:
- Packaging: confirm the code remains legible after production and that the destination will stay relevant for the product's expected shelf life.
- Events: test codes in venue lighting and confirm the redirect, offer, and fallback page remain active for the event dates.
- Retail displays: check visibility, scan distance, and whether the code is still positioned where shoppers can use it without obstruction.
- Direct mail: test the printed version, preserve the mailer-specific UTM content value, and keep the destination available after delivery delays.
After each review, mark the code as active, changed, paused, or archived. Remove access for former owners where appropriate, retain the campaign history, and confirm that inactive codes do not lead visitors to an error page or an unintended offer. A disciplined inventory and recurring link check turn QR reporting from a one-time launch task into dependable link analytics and reporting.
For larger sets of campaign links, combine this process with a bulk short link rollout workflow and a monthly marketing link governance audit.