Tag Docket
← All posts

How to track QR code scans in GA4: yard signs, mailers and events

GA4 doesn't count QR code scans. It counts the visits they start, and only if the link inside the code is tagged. How to tag printed pieces so GA4 credits them, stop them landing in Unassigned, and work out cost per scan.

Marcus Sanford QR codesPrintGA4

A client spends $4,000 on a mailer with a QR code on it. A month later they ask how it did. GA4 shows nothing obvious: no “Direct mail” channel, no line for the mailer, maybe a bump in Direct traffic or a few hundred sessions in Unassigned.

The mailer probably did work. GA4 just wasn’t told what it was looking at. GA4 doesn’t see a QR code scan at all. It sees a visit to a web page, and it knows only what the address of that page tells it. A QR code that holds a bare URL produces a visit with no source, which GA4 files as Direct. A QR code that holds a tagged URL produces a visit GA4 can credit.

Here’s how to set that up so every printed piece shows up in GA4, and what to do about the parts GA4 doesn’t handle by default.

The link inside the code needs the same UTM parameters as any other campaign link:

ParameterFor printExample
utm_sourceThe printed piecedirectmail, yardsign, vehiclewrap, homeshow
utm_mediumThe kind of offline trafficprint, offline or event
utm_campaignThe campaign, as for any other channelspring26_freeinspect_gutters
utm_contentWhat tells two batches apartnorthside, drop2

Lowercase, no spaces, and values from the client’s approved list, as in our UTM naming convention template.

utm_content is what makes print measurable at a useful level. Ten thousand mailers sent to two neighborhoods in two drops are four placements, and each one deserves its own value. Without it, all you can say is that “the mailer” brought visits.

A fully tagged URL is long, and a QR code gets denser as the text inside it gets longer. Denser codes need bigger prints, or they fail to scan from a distance. Put a short link in the code that redirects to the tagged URL.

The redirect has to do two things right:

  • Keep the tagging. If the redirect drops the query string, the visit arrives untagged and GA4 files it as Direct again. Test the short link and check that the address you land on still has its utm_ parameters.
  • Stay changeable. Printed pieces outlive their landing pages. Use a temporary redirect (302), not a permanent one (301), so you can point the code somewhere else later and phones that scanned before follow the change. The yard sign that outlived its landing page explains why.

3. Give offline traffic its own channel in GA4

GA4’s default channel grouping has no channel for print, events or offline traffic. A visit with utm_medium=print matches none of the rules, so it lands in Unassigned, next to traffic GA4 genuinely couldn’t classify. The spend looks as if it produced nothing.

Fix that with a custom channel group:

  1. In GA4, go to Admin → Data display → Channel groups.
  2. Create a new channel group. It starts as a copy of the default one.
  3. Add a channel called “Offline & QR”, with the condition Medium matches regex ^(print|offline|event)$.
  4. Save, then use the new channel group in the Traffic acquisition report, from the dropdown above the table.

The default channel group stays as it is; the new one sits alongside it. From then on, print shows up as its own line, with sessions, engagement and key events like any other channel.

4. Work out cost per scan

Once each placement has its own utm_content value, cost per scan is simple arithmetic: what that placement cost, divided by the sessions it brought. A $1,200 mailer drop that brought 300 sessions cost $4 a visit. Divide by the leads or sales it brought instead, and you have cost per lead.

Two cautions before reporting it to a client:

  • Scans aren’t the same as sessions. A link shortener or QR service counts scans at the redirect. GA4 counts sessions on the page. Phones that scan but don’t load the page, visitors who decline analytics cookies, and link previews all make the two numbers differ. Report which one you’re using.
  • Not every response scans. People also type the address, call the number or walk in. Pieces like radio and TV get no scans at all. For those, a promo code, a dedicated phone number or a hand count is the measure.

A checklist before the print run

  • The link in the code has source, medium and campaign, all lowercase with no spaces
  • Each placement has its own utm_content value
  • The short link redirects with a 302, and the landing page still shows the utm_ parameters
  • The landing page loads on a phone and has the GA4 tag on it
  • The code is big enough for the scan distance, with its quiet zone intact
  • GA4 has an “Offline & QR” channel for print, offline and event
  • The placement’s cost is written down somewhere you’ll find it in a month

You can run the finished link through the free UTM checker before it goes to the printer.

Where Tag Docket fits

Tag Docket does the parts of this that are easy to get wrong by hand:

  • Print links are built from each client’s approved values.
  • Short codes on its own short domain redirect with a 302 and keep the tagging.
  • QR codes are sized for the surface they’re printed on.
  • Each placement is logged with its dates, quantity and cost, so cost per scan is worked out for you.

The steps above work without it, too.

Bring the spreadsheet. We’ll show you the registry.

Start a free trial, no card needed. Your team signs in with an email link, no passwords.