Article5 min read

QR code tracking: how to see which printed code brought a visit

Track QR code scans in your web analytics with a UTM-tagged URL per placement. No QR platform needed, and each poster, flyer or package shows up as its own row.

By Glyphex ·

A QR code is just a URL in a format a phone camera can read. When someone scans it, their browser opens that URL and your analytics records a visit like any other. The trouble is that it usually records it as direct traffic: a scan carries no referrer, so the visit looks the same as someone typing your address. QR code tracking means giving each code a URL that identifies where it was printed.

Tag the URL, not the code

The reliable way to track QR code scans is to put UTM parameters in the URL before you generate the code:

https://example.com/menu?utm_source=table-card&utm_medium=qr&utm_campaign=winter-menu&utm_content=table-12
  • utm_medium=qr groups every printed code together, so you can compare QR traffic with email or social.
  • utm_source names the kind of placement: poster, flyer, packaging, table card, business card.
  • utm_campaign ties the code to what it promotes.
  • utm_content separates individual placements of the same campaign, for example one poster per location.

Any analytics tool that reads UTM parameters will then report scans as their own source, without a separate QR platform. The UTM builder produces the tagged URL so the parameter names stay consistent.

Static or dynamic codes

A static QR code encodes the final URL directly. It never expires and needs no third party, but you cannot change where it points once it is printed.

A dynamic QR code encodes a short redirect URL owned by a QR service, which forwards to your page. You can change the destination later, and the service counts scans. The cost is a dependency: if the subscription lapses or the service shuts down, every printed code stops working. If you use one, make sure the redirect keeps your UTM parameters intact, and check that the visit in your analytics is not attributed to the redirect domain.

For most printed material, a static code with a tagged URL is enough. Reprinting a flyer is cheaper than losing every code on it.

Make the URL short

Long URLs produce dense codes that are harder to scan from a distance or on small packaging. Keep paths short, and if the UTM string makes the code too dense, point the code at a short path on your own domain that redirects to the tagged URL. Your own redirect stays under your control.

Read the results

In your analytics, filter by medium qr and break down by source and content. Useful questions:

  • Which placement drives scans at all? A code nobody scans is a design or location problem.
  • Which placement drives visits that continue past the first page? Scans from a restaurant table and from a bus stop poster behave very differently.
  • Did scans rise after you moved or redesigned a code?

Set a goal on the action the code is meant to drive, such as a booking or signup, so you compare placements on outcomes rather than scans.

Common mistakes

  • One code reused across every placement, so all scans land in one undifferentiated row.
  • Inconsistent tag values, such as QR, qr-code and qr, which split one source into three.
  • No test scan before printing. Scan the final printed proof with two different phones and check that the visit appears in your real-time view with the right source.