A QR code does not provide reliable attribution by itself. To track a QR code campaign, connect each code to a clearly named campaign URL, add UTM parameters, generate a print-ready code, test the complete journey, and review scans alongside meaningful website actions. This workflow helps distinguish a code that was scanned from a campaign that actually performed.
Overview
A trackable QR code is usually a visual entry point to a URL. The QR image does not need to contain your analytics report; it needs to resolve to a destination that your analytics platform can identify. The most practical setup is a campaign URL with UTM parameters, optionally routed through a managed short link or redirect layer.
For example, a poster, product insert, and event badge might all lead to the same landing page but use different values for utm_source, utm_medium, or utm_content. This lets you compare placements without creating separate pages for every physical location.
A typical workflow is:
- Choose and verify the destination page.
- Define a naming convention for the campaign URL.
- Build the URL with a UTM builder or campaign URL builder.
- Generate a QR code using the final URL.
- Test the scan, redirect, page load, and conversion path.
- Record the code and placement in a campaign worksheet.
- Review performance on a planned cadence and before every reprint.
Keep the destination useful on a mobile screen. If the page is difficult to read, requires unnecessary steps, or does not match the printed call to action, scan volume will not tell the full story. If the destination needs to change later, a dynamic QR code or redirect-based link can make that change without replacing the printed artwork, provided the underlying service remains available and is monitored.
For campaigns that use a profile or collection of destinations, compare the landing-page requirements with the guidance in Link in Bio Tools Compared. For a simple campaign URL, document the naming rules described in UTM Parameters Explained.
What to track
Track enough information to explain performance later, not just enough to create the QR image. At minimum, capture the following fields for every code.
Destination and campaign identity
- Placement: Identify where the code appears, such as a storefront window, packaging insert, trade-show stand, or printed guide.
- Code version: Assign a simple identifier such as
poster-aorinsert-2026-q2. Do not reuse an identifier for a materially different placement. - Final destination: Record the complete URL and confirm that it is the intended mobile page.
- Redirect path: Note any short link, tracking domain, or redirect used before the destination.
UTM values
Use lowercase values and a consistent separator convention. A common structure might be:
utm_source=storefrontutm_medium=qrutm_campaign=spring_demoutm_content=window_a
The exact vocabulary matters less than consistency. Decide whether a physical location belongs in utm_source or utm_content, document that decision, and apply it to every code. Avoid changing names midway through a campaign because inconsistent values split reporting into separate rows. A URL parsing or normalization tool can help inspect encoded parameters and compare variants before publication.
Scan and conversion signals
Review scans or link visits, landing-page sessions, engaged visits according to your analytics setup, and the conversion event that reflects the campaign goal. That event might be a form submission, product action, app download, appointment request, or completed purchase. Do not treat every scan as a unique interested person: one person may scan more than once, and some scans may come from testing, previews, or automated systems.
Generator capabilities
When comparing a QR code generator, assess the workflow rather than the appearance alone.
| Feature | Why it matters | Questions to ask |
|---|---|---|
| Static or dynamic destination | Determines whether the printed code can support later destination changes. | Can the destination be updated, and what happens if the account or service is unavailable? |
| Campaign analytics | Provides scan-level or aggregate reporting alongside website analytics. | Which events, dates, devices, and locations are shown, and how are repeat scans represented? |
| Custom design controls | Allows the code to fit a brand or print layout. | Can the design preserve adequate contrast and a clear quiet zone? |
| Bulk creation | Reduces manual errors when producing multiple location-specific codes. | Can codes be imported from a validated URL list and exported with identifiers? |
| Destination management | Helps maintain links after publication. | Are edits, redirects, access permissions, and change history available? |
| Export quality | Supports reliable reproduction in different sizes and materials. | Are vector or sufficiently high-resolution files available for the intended print process? |
Campaign worksheet
Before approving artwork, create one row for each code:
| Field | Example entry |
|---|---|
| Placement | Reception counter |
| Code version | reception-a |
| Destination | https://example.com/demo |
| UTM values | source=office, medium=qr, campaign=summer_demo, content=reception_a |
| Scan date range | Start date through planned review date |
| Conversion metric | Completed demo request |
| Owner | Person responsible for checking the link |
| Last tested | Date, device, and result |
Cadence and checkpoints
Test the complete journey before the first print run, after any destination change, and whenever a new version of the artwork is produced. Scan the code from the actual printed proof rather than only from a design file. Check at least two mobile devices or camera apps when available, and test under the lighting and viewing distance expected in the real placement.
Use a redirect checker to confirm that the URL reaches the intended protocol and page without an unnecessary chain, loop, or unexpected error. The Redirect Checker Guide provides a practical framework for testing 301, 302, and HTTPS behavior. Also inspect the final URL to ensure UTM parameters remain intact after redirects.
During the campaign, a monthly check is suitable for many ongoing placements; high-value or time-sensitive campaigns may justify weekly review. Record:
- Scans or visits by code version and date.
- Landing-page sessions and conversion events.
- Errors, failed redirects, or unusual drops.
- Destination changes and the person who approved them.
- Physical changes, such as a poster being moved, covered, or damaged.
At the end of the planned scan date range, preserve the report and mark the code as active, paused, replaced, or retired. For large sets of URLs, validate them in bulk before launch and use link monitoring to detect destination changes after publication. See How to Validate Bulk URLs Before a Campaign Launch and Outbound Link Monitoring Tools for related workflows.
How to interpret changes
A change in scan volume is a signal to investigate, not a conclusion about campaign quality. Start by comparing the same date range and code versions. A code placed in a high-traffic area may naturally receive more scans than one in a quiet location, while a code that is hard to see or scan may underperform even when the offer is strong.
Use a simple diagnostic sequence:
- Check availability: Scan the code and confirm the redirect, page load, and mobile layout.
- Check attribution: Verify that the expected UTM values reach analytics and are not stripped by a redirect.
- Check the funnel: Compare scans with sessions, page interactions, and the defined conversion metric.
- Check the physical context: Review placement, size, contrast, glare, viewing distance, and the call to action.
- Check data quality: Separate internal tests, repeated visits, previews, and suspicious bursts from normal campaign activity where your tools allow.
A high scan count with few conversions can indicate a mismatch between the printed promise and landing page, a slow or confusing mobile experience, or a conversion event that is not being recorded correctly. A low scan count with a healthy conversion rate may suggest that the offer and page work, but the placement or visibility needs attention. Avoid comparing generator scan counts directly with analytics sessions without checking how each system defines a scan, visit, repeat user, and date.
For security and maintenance, review branded short links and access controls before sharing campaign URLs. The Short Link Security Checklist can support that review.
When to revisit
Revisit this workflow before every print run, whenever a destination page or redirect changes, and at least monthly or quarterly for long-running placements. Refresh the article and your internal process about every six months to account for changes in generator capabilities, analytics terminology, mobile-browser behavior, and print-production guidance.
Before reprinting, complete this short checklist:
- Confirm that every destination is current and accessible.
- Regenerate or re-export codes only from approved, final URLs.
- Compare UTM values with the campaign naming convention.
- Scan physical proofs at the intended size and viewing distance.
- Check contrast, quiet space, material finish, and surrounding design.
- Record the code version, placement, owner, date range, and conversion metric.
- Retire or redirect old versions deliberately rather than leaving them undocumented.
After the campaign, compare locations and code versions using the same definitions and date ranges. Keep the worksheet with the performance review so the next print decision is based on both attribution data and the physical conditions in which the QR code appeared. That combination makes QR code analytics useful beyond a single scan total: it turns each offline placement into a maintainable, testable link workflow.