Can You Track a QR Code in Google Analytics? The Honest Answer

Short answer: yes, indirectly. Google Analytics 4 cannot see the QR code itself, but it can see every visit that arrives from a URL tagged with UTM parameters. One tagged code per placement gives you sessions, engagement and key events (purchases, sign-ups, bookings) for each poster, flyer or package. What it does not give you is a count of scans that never loaded the page.

A QR code is a picture of some text — usually a web address. When a phone reads it, nothing is sent back to the code, the printer or the tool that made it. So the code itself can never tell you how often it was scanned. What you can measure is what happens at the other end: the moment that scan arrives somewhere you control.

There are two places that can do the counting:

How to track QR code scans using UTM parameters, Google Analytics 4 and short links
Three layers: UTM parameters tag each source, GA4 reports the visits, and an optional short link on your own domain adds a server-side count.

To be clear about our own tools: the free web generator, Gen QR for Mac and Tab to QR all make static codes and include no scan analytics — deliberately, since they run on your device and collect nothing. That is not a dead end. The route below gives you per-placement numbers in an analytics account you already own, with no extra subscription and no third party sitting between your customers and your site.

Dashboard showing QR code scan analytics with charts for scans over time, location heat map, and device breakdown
The goal: turn printed codes into numbers you can compare, placement by placement.

UTM Parameters for QR Codes

UTM (Urchin Tracking Module) parameters are tags added to the end of a URL. They do nothing to the page itself; they simply tell your analytics where the visit came from. GA4 reads them automatically — there is no code to add to your site beyond the normal GA4 tag.

UTM parameters used in QR code tracking: utm_source, utm_medium, utm_campaign and utm_content with example values
Four UTM tags on one QR code URL. Use lowercase names and underscores consistently across every campaign.

There are five standard UTM parameters; QR campaigns typically use four:

Parameter What it records QR example GA4 dimension
utm_source Where the visit came from qr Session source
utm_medium The kind of channel print, packaging, signage Session medium
utm_campaign The campaign or promotion spring_menu_2026 Session campaign
utm_content Which placement or version table_tent, window_poster Session manual ad content

A complete tagged URL looks like this:

https://www.example.com/menu?utm_source=qr&utm_medium=print&utm_campaign=spring_menu_2026&utm_content=table_tent

The trick that makes QR tracking useful is one code per placement. The table tents, the window poster and the flyer each get their own utm_content value and therefore their own QR code. Later, GA4 can tell you which one pulled its weight.

Naming Rule

UTM values are case-sensitive in reports: QR, qr and qr-code show up as three different sources. Pick one convention (lowercase, underscores), write it down in a shared sheet, and reuse it for every campaign.

Build the Tagged URL with Google’s Campaign URL Builder

You do not need to type UTM parameters by hand. Google publishes a free Campaign URL Builder that assembles the URL for you. The steps are the same every time:

  1. Enter the Website URL — the exact page the code should open, starting with https://.
  2. Fill in Campaign source, Campaign medium and Campaign name. These three are the required fields; they become utm_source, utm_medium and utm_campaign.
  3. Add Campaign content (utm_content) to identify the placement. The builder also has optional fields for campaign ID (utm_id) and campaign term (utm_term); for printed QR codes you can usually leave both empty.
  4. Copy the generated URL, open it in a browser once to be sure the page loads, and paste it into the free QR generator.

Two details save headaches later. First, avoid spaces and special characters in values, because they get percent-encoded and make the URL longer and harder to read in reports. Second, if the destination page already has a query string (for example ?lang=en), the tags must be joined with &, not a second ?; the builder handles this for you.

UTM Naming Conventions That Keep QR Reports Clean

GA4 reads UTM values exactly as written, so QR, qr and Qr become separate rows. Decide the rules before the first print run and keep them in a shared sheet. A convention that works for most small teams:

ParameterRuleGoodAvoid
utm_sourceOne fixed value for all QR trafficqrQR, qrcode, QR Code
utm_mediumPhysical format, from a short fixed listprint, packaging, signageflyer-march (that is a campaign)
utm_campaignPromotion name plus year or monthspring_menu_2026New Menu!!
utm_contentPlacement or version, unique per codetable_tent, window_poster1, final_v2

Never use UTM parameters on links inside your own website. They start a new session and overwrite the real source of the visit; they belong only on links that bring people to your site from outside, which is exactly what a printed QR code does.

How to Set Up QR Code Tracking in GA4 (5 Steps)

This assumes your site already has the GA4 tag installed. If it does, you are about ten minutes from your first tracked code.

Five steps to set up Google Analytics 4 tracking for a QR code campaign, from UTM URL to custom Exploration
Five steps from tagged URL to report. Scan the code yourself and confirm the visit appears in GA4 Realtime (dashboard figures are illustrative).

Track a QR Code in Google Analytics 4

1

Build the tagged URL. Use Google’s free Campaign URL Builder or type the parameters yourself. Set utm_source=qr, a medium, a campaign name and a utm_content value for this placement.

2

Turn it into a QR code. Paste the whole tagged URL into the free generator and download PNG or SVG. For a branded version with your colours or logo, use Gen QR on a Mac. Repeat for each placement.

3

Scan it and check Realtime. Scan the code with your phone, then open Reports > Realtime in GA4. Your visit should appear within a minute or so with the source and campaign you set. If it shows up as direct traffic, the parameters were lost — check the URL you encoded.

4

Open Traffic acquisition. Go to Reports > Acquisition > Traffic acquisition, change the table’s primary dimension to Session source / medium or Session campaign, and search for qr.

5

Save an Exploration. In Explore, build a free-form report with Session source, Session campaign, Session manual ad content and Landing page as dimensions, and Sessions, Engaged sessions, Key events (called Conversions before 2024) and Total revenue as metrics. Save it as your QR dashboard.

Step-by-step illustration showing UTM URL creation, QR code generation, and GA4 traffic acquisition report
Build a UTM URL, generate the code, then watch the results arrive in GA4.
Testing Shortcut on a Mac

Open the tagged URL in Safari, click Tab to QR in the toolbar and scan the code straight off your screen. It is a quick way to check that the exact URL — parameters and all — reaches GA4 Realtime before you send anything to print.

Test Before You Print: Realtime and DebugView

Always test the exact URL that is inside the code, on a phone, before a print run. Two GA4 tools help:

Remember that Realtime is instant but the standard reports are processed more slowly; Google notes that data in standard reports can take 24 to 48 hours to appear in full. Do not judge a campaign from the first morning’s numbers, and do not panic if Traffic acquisition looks empty an hour after launch — check Realtime first.

Where to See QR Code Scans in Google Analytics 4

Once codes are out in the world, these are the places to look:

One thing that surprises people: GA4’s default channel grouping does not have a “print” or “QR” channel, so traffic tagged utm_medium=print can appear as Unassigned in the channel view. Nothing is broken — switch the dimension to source / medium or campaign and the QR traffic is all there.

Build a QR Exploration step by step

  1. In GA4 open Explore and start a blank Free form exploration.
  2. Under Variables, import the dimensions Session source / medium, Session campaign, Session manual ad content and Landing page, and the metrics Sessions, Engaged sessions, Key events and Total revenue.
  3. Drag Session campaign and Session manual ad content into Rows, and the metrics into Values.
  4. Add a filter: Session source / medium contains qr. Save the exploration and name it “QR codes”.

Traffic acquisition reports on sessions (each visit); the User acquisition report instead groups people by how they first arrived. For a poster that wins a first visit and a purchase later, compare both: the session view tells you which code was scanned, the user view tells you which channel first introduced the person to you.

If you have key events set up (purchases, bookings, sign-ups, form submissions), the same reports show how many of them came from each code. That is the raw material for working out QR code ROI.

Shorter Codes and a Second Count: Redirects on Your Own Domain

UTM parameters make URLs long, and a long URL makes a denser code that needs to be printed larger. The fix is a short address on your own domain that forwards to the tagged page:

yoursite.com/q/menu → https://www.yoursite.com/menu?utm_source=qr&utm_medium=print&utm_campaign=spring_menu_2026&utm_content=table_tent

What a redirect you own adds

Keep the Tags on the Destination

The UTM parameters must be on the URL the visitor finally lands on, because that is the page where GA4 runs. Put them on the redirect target (as above), test the chain once with your phone, and confirm the campaign appears in Realtime.

Generate a Tagged QR Code Free

Paste your UTM-tagged or short URL and download PNG or SVG in seconds. Nothing uploaded, no account.

What You Can Measure (and Where to Find It)

With one tagged code per placement, GA4 gives you six numbers worth watching:

Six key QR code tracking metrics: total scans, unique users, location, device and OS, time of day and conversion rate
Six metrics that show where scans come from and what they achieve (dashboard numbers are illustrative).
Metric What it tells you Where in GA4
QR sessions Visits that arrived through your codes — the closest analytics gets to “scans” Traffic acquisition, filtered to source qr
Users Distinct people, so a regular who scans the menu every week counts once Total users in the same report
Placement Which code (table tent, poster, flyer) drove the visit Session manual ad content in an Exploration
Device & OS iPhone vs Android split — tells you what to test the landing page on Tech details report, or Device category in an Exploration
Location & time Which cities and which hours scans come from Demographic details report; Hour dimension in an Exploration
Key events How many QR visitors bought, booked or signed up Key events column, broken down by campaign or content
Six metric cards showing total scans, unique users, location map, device split, time-of-day chart, and conversion rate
The six core numbers that turn QR visits into placement decisions.

There is no universal “good” scan or conversion rate — it depends entirely on the audience, the offer and where the code sits. What matters is your own baseline: run two placements side by side for a few weeks, compare sessions and key events per placement, and move budget toward the one that wins.

Download

QR Code Apps for Mac & Safari

Prefer generating codes without opening a browser tab? These two native Apple apps cover both habits — a full generator on the desktop, and a one-click share button inside Safari.

Gen QR Fast QR code generator for links, text, Wi-Fi and vCards. Works fully offline, exports PNG and SVG.
Mac App Get
Tab to QR Turn the current tab into a QR code to scan or share, straight from the Safari toolbar.
Safari Extension Get

Attribution: How GA4 Credits a QR Scan

A scan is often one step in a longer journey. Someone scans your poster, browses, leaves, and buys a week later from a Google search. Which channel gets the credit depends on the attribution model.

Last-click

All the credit goes to the last touchpoint before the conversion. GA4’s Traffic acquisition report credits each session to its source, and GA4’s attribution settings still offer a “paid and organic channels last click” model next to the data-driven one. It works well when QR is a direct-response channel (scan, then order), but undervalues codes that mainly introduce people to you.

Data-driven

GA4’s default model uses machine learning to share credit across all touchpoints based on how much each one contributed. It suits multi-channel campaigns, but with low key-event volume the results are less stable, so smaller campaigns often get clearer answers from last-click reporting.

First-click and position-based

First-click gives all credit to the first touch; position-based (U-shaped) gives 40% to the first touch, 40% to the last and shares the remaining 20% across the middle. Both are useful for judging QR as a discovery channel. Note that GA4 retired its first-click, linear, time-decay and position-based models in late 2023, so you would apply these in a spreadsheet or another analytics tool.

Whichever you choose, use it consistently. Switching models mid-campaign makes your before-and-after comparisons meaningless.

Troubleshooting: Why QR Traffic Does Not Show Up Correctly

SymptomLikely causeFix
Scans appear as DirectA redirect or app dropped the UTM parametersMake the redirect pass the query string, or put the tags on the redirect’s final target URL
Traffic shows as Unassigned in the channel viewGA4’s default channel grouping has no rule for a medium such as printSwitch the report to Session source / medium or Session campaign
Same code split across several rowsInconsistent capitalisation or spellingUse one lowercase convention; fix the printed URL going forward
Nothing in RealtimeGA4 tag missing on the landing page, or a consent banner blocking it until the visitor acceptsCheck the tag on the exact destination page and your consent settings, then test again
QR visits look low versus print runPeople scanned but did not load the page, or declined analytics cookiesCompare placements against each other rather than against print numbers
Own-site clicks overwrite the sourceUTM tags used on internal linksRemove UTMs from links inside your site

If you use a redirect on your own domain, use a temporary (302) redirect for destinations you may change later, so browsers do not cache the old target, and always re-test after any server change.

What This Setup Can’t Tell You

Static code plus UTM plus GA4 is the right starting point for almost everyone, but it is worth knowing its edges:

Capability Static code + UTM + GA4 + Redirect on your domain Subscription dynamic code
Visits & key events per placement Yes Yes Yes, if you also tag the URL
Count independent of analytics consent No Server log Platform log
Change destination after printing No Yes Yes
Works if a third party shuts down Yes Yes No
Ongoing cost Free Your hosting Monthly or yearly fee

Whichever way you go, the rule is the same: never put an untagged code into the world. Even a single utm_source=qr beats having no idea what the print run achieved. For more on making the link itself, see how to create a QR code for a URL, and for the trade-offs of editable codes read static vs dynamic QR codes.

Frequently Asked Questions

Not from the code itself. A QR code is just a printed pattern; it cannot report anything. Scans are counted at the place the scan lands: either a redirect server that the code points to, or the analytics on your own website. With a static code and a UTM-tagged URL, Google Analytics 4 counts the visits that each code sends, which is the number most people actually need.

Yes, indirectly. Encode a URL with UTM parameters, such as ?utm_source=qr&utm_medium=print&utm_campaign=spring_menu, and GA4 records every visit that arrives through the code, along with what the visitor did next. You will not get a count of scans that never loaded the page, but you do get sessions, users, devices, locations and key events.

Build a tagged URL with utm_source, utm_medium and utm_campaign (plus utm_content for each placement), turn it into a QR code, and scan it yourself to confirm the visit appears in Reports > Realtime. After that, open Reports > Acquisition > Traffic acquisition and switch the table dimension to Session source / medium or Session campaign to see the QR traffic, engagement and key events.

Use three as a minimum: utm_source (for example qr), utm_medium (print, packaging or signage) and utm_campaign (spring_menu_2026). Add utm_content to tell placements apart, such as table_tent versus window_poster. Keep everything lowercase with underscores so the values group cleanly in reports.

No. Dynamic codes from subscription platforms count scans at their redirect, but GA4 plus UTM tags on a static code already shows visits and conversions per placement for free. If you also want a server-side count or a shorter printed URL, point the code at a redirect on your own domain, such as yoursite.com/q/menu, and keep the UTM tags on the page it forwards to.

GA4 only counts visits where its tag loads and is allowed to run. People who decline analytics cookies, use content blockers, close the page before it loads or open the link in an in-app browser that blocks scripts may be missing or modelled. Treat GA4 numbers as a reliable comparison between placements and campaigns rather than an exact headcount of scans.

Use utm_source=qr, a utm_medium that names the physical format (print, packaging or signage), a utm_campaign for the promotion, and a unique utm_content for each placement. Keep everything lowercase with underscores and build the URL with Google’s Campaign URL Builder so the format is identical every time.

Open Reports > Acquisition > Traffic acquisition and change the primary dimension to Session source / medium or Session campaign. Right after a test scan, check Reports > Realtime. For placement-level detail build a free-form Exploration with Session manual ad content.