September 20, 2026 · By Dhurka Manchukan, Software Engineer · Guides · 3 min read
How to track QR code campaigns with UTM parameters
Printing a QR code on a poster is easy. Knowing whether the poster was worth printing is harder. UTM parameters solve that by adding small labels to your link so your analytics tool can tell you exactly where each visit came from.
What UTM parameters are
UTM parameters are short tags added to the end of a URL, such as ?utm_source=poster&utm_medium=qr&utm_campaign=autumn-sale. Analytics tools read them and group visits accordingly. They do not change what the visitor sees; they only tell you how they arrived.
- utm_source: where the traffic comes from, for example a specific poster, flyer or partner.
- utm_medium: the type of channel, such as qr, print or email.
- utm_campaign: the name of the campaign, for example autumn-sale.
- utm_content: optional, to tell apart two versions or two placements of the same campaign.
- utm_term: optional, mainly used for paid search keywords.
Why they matter for QR codes
A QR code bridges the physical and digital worlds, and by default that bridge is invisible to your website analytics. Without tagging, visits from a printed code often show up as direct traffic, mixed with everyone who typed your address. Tagging the destination lets you separate them.
A simple naming convention
The value of UTM data depends on consistency. If one person writes Poster and another writes poster, analytics treats them as different sources. Agree a convention and stick to it.
- Use lowercase only.
- Use hyphens instead of spaces.
- Keep utm_medium the same for every QR code, for example qr.
- Make utm_source specific: cafe-window, station-poster, flyer-march.
- Keep a shared spreadsheet listing every tagged link you create.
Building and using a tagged link
Start with the full landing page address, add the parameters, then use that tagged address as the destination of your QR code. With a redirect-based code you can even change the destination later while keeping the tags, so the printed code stays valid for the whole campaign.
Reading the results
In your analytics tool, open the acquisition or campaign report and filter by the medium you used for QR. Compare sources to see which placements bring visits, then look beyond visits: do those visitors stay, sign up or buy? A poster with fewer scans but more purchases may be the better placement.
Combine UTM data with scan analytics
Scan counts from the QR platform tell you how many people scanned; UTM data in your analytics tells you what they did afterwards. Together they show the whole journey: scanned, arrived, converted. A big gap between scans and visits can point to a slow landing page or a broken link.
Common mistakes
- Tagging internal links on your own site, which overwrites the true source of a visit.
- Inconsistent capitalisation that splits one source into several.
- Using long, messy campaign names that are hard to read in reports.
- Forgetting to test the tagged link before printing.
A worked example
Suppose a gym prints three posters for a January membership offer: one at the front desk, one in a nearby cafe and one at a bus stop. Each poster has its own QR code that leads to the same landing page, but with a different source tag, such as utm_source=front-desk, utm_source=cafe-window and utm_source=bus-stop, all sharing utm_medium=qr and utm_campaign=january-offer.
After two weeks the campaign report shows that the bus stop poster brought the most visits, but the cafe poster produced the most sign-ups. Without tagging, all of that would have been a single lump of direct traffic. With it, the gym can decide to put the next poster budget into the cafe placement and reconsider the bus stop.
Respecting privacy while measuring
UTM tags describe where a visit came from, not who the visitor is, so they are a privacy-friendly way to measure print. Still, be honest about your analytics in your privacy policy, and never put personal information such as an email address or name into a URL parameter, because URLs are stored in browser history and server logs.
Done consistently, UTM tagging turns every printed code into a small experiment you can learn from, at no extra cost.
Written by
Dhurka Manchukan
Software Engineer · Sri Lanka
Dhurka Manchukan is a software engineer based in Sri Lanka and the person behind MDXTORA. Dhurka designs, builds and runs QRinst, Faviqo and Wayvert, and writes the articles in the Journal from what comes up while building them.
About the author →Keep reading
- GuidesHow to estimate a trip budget before you bookA practical way to estimate what a trip will cost: the four daily categories, how to handle flights and currency, and how much buffer to add.
- GuidesFavicon sizes in 2026: what you actually needA practical guide to favicon and app-icon sizes, which files browsers and phones request, and how to link them correctly.
- GuidesCommon QR code mistakes and how to avoid themThe most frequent reasons QR codes fail in the real world, from poor contrast to broken links, and how to prevent each one.
