Home / Blog / Measurement

Measurement

How to Track QR Code Campaign Visits with UTM Parameters

By QRNest · Published October 28, 2026 · 3 min read

Build a consistent UTM-tagged QR destination, test attribution and understand why website visits are different from total QR scans.

Understand what your report can count

The QR image itself does not call an analytics server just because a camera recognizes it. A person may preview the link without opening it, close the page before it loads or decline optional tracking. A URL may also be copied and shared with people who never scanned the code.

Report a metric such as “recorded visits from the counter card,” rather than presenting it as an exact scan total. If a redirect service supplies scan-like counts, document its definition too. Redirect requests, analytics sessions and completed purchases describe different stages.

Choose a naming plan before printing

Use a consistent source, medium and campaign name. Add content when you need to distinguish placements. Google's Analytics documentation describes these campaign parameters and notes that their values are case-sensitive.

The custom medium qr is an internal naming choice, not a guarantee of a built-in QR channel in Analytics. Check how your reporting groups it. Keep spelling and capitalization consistent so one campaign does not fragment across several labels.

Build and generate a testable destination

https://example.com/workshop?utm_source=store_counter&utm_medium=qr&utm_campaign=autumn_workshop&utm_content=green_card

1. Choose the landing page and confirm it works on a phone.
2. Add the agreed UTM parameters using a URL builder or URL library.
3. Open the full address and confirm redirects preserve the needed parameters.
4. Generate a website QR code in QRNest using that complete address.
5. Scan the downloaded image and check your destination's analytics using its testing tools.
6. Record the final URL alongside the design file and placement name.

Do not put names, email addresses, customer identifiers or confidential details in campaign parameters. They are part of the URL and can appear in browser history, logs and shared links. A campaign label should describe a placement, not identify an individual.

Confirm the destination actually captures attribution

Adding UTM parameters does not install analytics or override consent settings. Your destination must collect the relevant campaign information under its own configuration. Some privacy-focused implementations deliberately remove query parameters before sending page data; those setups may not attribute these visits from UTMs.

QRNest generates the encoded URL, but does not supply a scan dashboard for downloaded static codes. Its own consent-based page measurement also omits URL query strings. To measure your campaign, verify the analytics behavior of your own landing page rather than assuming every website records the parameters.

Judge the campaign by the useful action

Pair recorded traffic with a meaningful outcome such as completed registrations, qualified enquiries or document downloads where measured appropriately. A busy sign can generate visits without delivering the result you wanted. Compare placements over a similar period and keep material changes, like a new offer, in your campaign notes.

This guide describes the current QRNest tools. Other apps and destination services may behave differently. Report an error or suggest an update.