QR Code Tracking: How It Works, What You Can Measure, and How to Do It Free (2026)

Most “QR code tracking” tutorials skip the part you actually need to understand: how the tracking happens, what data you get, and whether you really need to pay for it. (Spoiler: you don’t.) This guide breaks down QR code tracking end-to-end — the mechanism, the data, the setup, and the free path most competitors won’t tell you about.

QRelix is free to start, with no credit card required, and tracking is included on the free tier — not behind a paywall like most generators charge for. By the end of this post, you’ll know exactly how QR code tracking works under the hood and how to set up your first trackable QR code in under a minute.

What “QR code tracking” actually means

QR code tracking is the practice of measuring what happens after someone scans a QR code — how many scans, when they happened, where they happened, and what device the user was on. The QR code itself isn’t doing the tracking. It’s the destination link that captures the data, the same way any web link can be tracked.

That distinction matters because it explains why tracking only works for certain types of QR codes:

• A QR code that points directly to https://yourbrand.com/page has no built-in tracking. Whatever analytics that page already has (Google Analytics, Plausible, etc.) is what you get — and you can’t distinguish scans from regular web traffic.
• A QR code that points to a trackable redirect URL (like qrelix.com/r/abc123) routes every scan through a tracking layer first, then redirects to your destination. That intermediate step is what captures the scan data.

This is why “static” QR codes (which encode the final URL directly) can’t be tracked natively, while “dynamic” QR codes (which encode a redirect URL) can. For the full breakdown on the difference, see our guide to what a trackable QR code is.

How QR code tracking works under the hood

Here’s the exact technical flow on every scan of a trackable QR code:

1. User scans the QR code. Their phone camera reads the encoded URL — for a trackable QR, this is a short redirect URL pointing to the tracking service (e.g., qrelix.com/r/abc123).
2. The redirect URL hits the tracking server. Before sending the user anywhere, the server logs the request: timestamp, IP address (which maps to city/region/country), user agent (which reveals device type, OS, and browser), and referrer.
3. The server issues a 302 redirect. The user’s browser is sent to the final destination URL — your landing page, menu, form, or wherever you’ve configured.
4. The destination loads. From the user’s perspective, the scan is instant. They see the destination page within a second of scanning.

The whole hop adds 50–200 milliseconds at most. Users don’t notice it. The tracking service does the data capture; you log into a dashboard to see the results.

This is the same architecture used by every link shortener (Bitly, TinyURL, Linktree) and every paid QR code platform. There’s no proprietary magic — the difference between providers is what data they show you, how long they retain it, and how much they charge.

What data you can capture on every scan

A well-built QR code tracking platform captures all of the following with no extra setup on the user’s end:

Scan volume

Total scans, unique scans (deduped by device or IP), and scans over time. This is the baseline metric and the one most people care about: “Did people actually scan this?”

Time of scan

Date, time, and day-of-week breakdowns. This tells you when your audience engages — useful for everything from restaurant menu drops (lunch vs. dinner) to event check-ins (registration peaks).

Geographic location

City, region, and country, derived from the scanner’s IP address. Useful for measuring physical campaign reach (which store locations are driving the most scans, which trade show booth performed best, which markets responded to a billboard).

Device type and OS

iOS vs. Android, phone vs. tablet, browser. Useful for diagnosing landing page issues (e.g., your menu PDF renders weirdly on iOS Safari and you’re losing those users).

Referrer (sometimes)

Where the scan request came from. For most direct camera scans, this is empty — but when QR codes are embedded in PDFs, screenshots, or email clients, you’ll sometimes see referrer data that helps you attribute the scan to a specific surface.

What you can’t capture from the QR code layer alone: who the user is, their email address, what they did on the destination page, whether they converted. Those require either an authenticated user, a form submission, or analytics on the destination page itself. For the full breakdown of what tracking does and doesn’t see, see our post on trackable QR code data explained.

The two paths to tracked QR codes

There are two legitimate ways to get tracking on a QR code, and they’re often confused:

Path 1: Static QR + UTM parameters

You generate a regular (“static”) QR code that points to a URL with UTM parameters appended — for example:

https://yourbrand.com/promo?utm_source=qr&utm_medium=print&utm_campaign=spring-sale

When users scan it, the UTM tags flow into your existing analytics platform (Google Analytics 4, Plausible, etc.). You see the scan traffic in your normal analytics dashboard, segmented by source.

Pros: No third-party redirect, no extra service required if you already have analytics.

Cons: The destination URL is baked into the QR image — you can’t change it later without reprinting. You can’t see scan volume independently of regular web traffic if users also reach the page through other channels. If you don’t already have GA4 set up correctly, the data is invisible. For the full walkthrough on this approach, see QR code tracking in Google Analytics 4.

Path 2: Dynamic QR + built-in tracking dashboard

You generate a dynamic QR code through a tracking platform. The QR image encodes a short redirect URL; the platform captures every scan and shows the data in a built-in dashboard. You can also change the destination URL anytime without regenerating the QR code.

Pros: Dashboard works out of the box, no analytics setup required, the destination is editable post-print, scans are isolated from organic web traffic, and you can run multiple campaigns from multiple QR codes and compare them side-by-side.

Cons: Depends on the tracking service staying online. (Pick one that doesn’t expire QR codes or paywall basic analytics after a trial — see our breakdown of hidden costs in free QR generators.)

For most use cases — especially anything printed or anything where you might want to update the destination later — Path 2 is the right answer. It’s also what makes the free path possible: with QRelix, dynamic QR codes and the tracking dashboard are included on the free tier.

How to set up QR code tracking free in under a minute

Here’s the fastest path to a working trackable QR code with no card and no trial timer:

1. Go to qrelix.com and create your first QR code free. No signup required to generate, but signing up unlocks the tracking dashboard.
2. Choose “Dynamic QR” so tracking is built in. (Static QR codes can’t be tracked from the QR layer alone — see above.)
3. Paste your destination URL. This is wherever you want scanners to land: a landing page, menu, form, payment link, anything.
4. Optionally name the QR so you can find it later in your dashboard. (“Spring Sale Flyer,” “Table Tent v2,” etc.)
5. Download the QR image in PNG or SVG and ship it — print, embed, share, post.
6. Watch scans land in your dashboard in real time. Filter by date, location, or device.

That’s the whole flow. No 14-day trial, no surprise expiration, no “upgrade to see scan data” wall. Scan volume, location, device, and time are all included on the free tier. (Paid tiers add team workspaces, higher scan volumes, and advanced features — but the core tracking everyone actually needs is free.)

For a step-by-step walkthrough with screenshots, see how to create a trackable QR code.

QR code tracking vs. QR code analytics — what’s the difference?

These terms get used interchangeably, but they’re not the same thing:

• QR code tracking is the raw capture: every scan logged with metadata.
• QR code analytics is what you do with that capture: trends over time, segmentation, A/B comparisons, conversion attribution.

Most tracking platforms include some level of analytics in the dashboard — daily/weekly charts, top locations, device breakdowns. Heavier analytics (cohort analysis, funnel attribution into your CRM, multi-touch campaign reporting) usually requires either an enterprise plan or piping the scan data into a tool like GA4, Mixpanel, or your data warehouse.

For most small and mid-sized campaigns, the built-in analytics in the tracking dashboard is more than enough. You don’t need a data team to know whether your flyer worked.

Common QR code tracking mistakes

A few things that trip people up — easy to avoid once you know about them.

Tracking a QR code that’s already printed. If the QR image encodes a direct URL (no redirect layer), you can’t add tracking after the fact without reprinting. Always start with a dynamic QR if there’s any chance you’ll want to track or change the destination later.

Using a “free” tool that expires your QR after 14 days. This is the most common trap in the QR space. Make sure your provider doesn’t kill the QR or block analytics after a trial. (QRelix doesn’t — the free tier doesn’t expire.) See what’s truly free vs. what will cost you later.

Comparing scan totals to website pageviews and panicking. Scans are almost always a fraction of pageviews because they require a real-world action. A scan-to-pageview ratio of 1:50 isn’t bad — it’s normal. Judge QR campaigns against the cost of the physical placement, not against digital benchmarks.

Ignoring uniques vs. total scans. Total scans counts every tap of the QR; uniques dedupe. The difference matters: 500 total / 50 unique means your audience is engaging multiple times (often good for menus, schedules). 500 total / 500 unique means broad reach with no re-engagement (often a sign your destination isn’t sticky).

Not naming your QR codes. If you run more than three campaigns, you’ll forget which QR is which inside a month. Name them at creation. Future-you will say thank you.

When QR code tracking actually pays off

Tracking is most valuable when you’re spending money on physical placement and need to know which placements drive results. Some concrete examples:

• Print ads: Different QR per publication tells you which magazine, newspaper, or direct-mail piece actually drove scans.
• Trade shows and events: Different QR per booth, kiosk, or session lets you measure individual session attribution instead of guessing.
• Retail signage: Different QR per store location reveals which locations have engaged customers vs. which need help.
• Product packaging: Tracked QR codes on packaging show ongoing customer engagement long after purchase.
• Restaurant menus: Track scan timing to see lunch vs. dinner engagement and which menu sections drive the most clicks.
• Real estate signs: Per-listing QR codes let you measure interest before a single agent call.

If you’re just printing one QR on one flyer for one event, basic tracking is plenty — and free is the only price that makes sense. If you’re running dozens of placements across multiple campaigns, structured tracking with per-QR naming and segmentation is what separates “we ran a QR campaign” from “we know the print spend in Region 3 outperformed Region 1 by 4x.”

Get tracking on your next QR code in under a minute

QR code tracking isn’t complicated, and it isn’t something you should be paying $15/month for on top of every other SaaS bill. The mechanics are simple — a redirect layer captures the scan, your dashboard shows the data — and the core feature set every campaign actually needs (scan volume, location, device, time) is available free on QRelix with no card, no trial timer, and no surprise expiration.

Create your first trackable QR code free — no credit card required.

Want to see exactly what’s on each tier before you start? See what’s included free.

# Example of a single QR scan hitting a dynamic redirect URL

GET /r/abc123 HTTP/1.1
Host: qrelix.com
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 17_0 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Mobile/15E148 Safari/604.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.9
X-Forwarded-For: 203.0.113.42
Referer: 

HTTP/1.1 302 Found
Location: https://yourbrand.com/promo?utm_source=qr&utm_medium=print&utm_campaign=spring-sale
Cache-Control: no-store

# On the server side, the tracking platform logs something like:
# - timestamp: 2026-03-14T12:34:56Z
# - qr_id: abc123
# - ip: 203.0.113.42 (geo-resolved to city/region/country)
# - user_agent: "Mozilla/5.0 (iPhone; ... Safari/604.1)"
# - device_type: mobile
# - os: iOS
# - browser: Safari
# - referrer: null
# - destination_url: https://yourbrand.com/promo?utm_source=qr&utm_medium=print&utm_campaign=spring-sale