The Fundamental Distinction: Static vs Dynamic
QR code tracking hinges on one critical distinction: whether your code is static or dynamic.
Static QR codes encode the destination URL directly into the code's visual pattern. When someone scans a static code, their phone reads the URL and goes directly there. There's no intermediary, no server involved in the redirect, and therefore no opportunity to count the scan. Static codes cannot be tracked at the QR level.
Dynamic QR codes work differently. They encode a short redirect URL (like qr.example/abc123) that points to a server controlled by the QR code provider. When someone scans, their phone goes to that server first. The server logs the request, counts the scan, and then redirects to the actual destination URL. This redirect happens in a fraction of a second, but it's what enables all tracking.
This is why dynamic QR codes are a paid feature on most platforms. The provider is running a redirect service, storing scan data, and providing an analytics dashboard. Static codes cost nothing to maintain because they don't require any ongoing server infrastructure.
What Data Can QR Code Analytics Capture?
When a dynamic QR code is scanned, the redirect server can capture various types of data. Here's what's typically available:
Scan Count
The most basic metric: how many times has this code been scanned? This is the foundation of all QR analytics. Most platforms show total scans and may distinguish between total scans (including multiple scans from the same person) and unique scans (attempting to count individual people).
Time and Date
When did the scans happen? Analytics dashboards typically show scans over time-by day, by hour, or both. This is valuable for understanding when your audience is engaging with your code. A restaurant menu QR code might see peaks at lunch and dinner times. A conference QR code might spike during specific sessions.
Geographic Location
Where are people scanning from? QR code platforms use IP geolocation to determine the approximate location of each scanner. This usually shows country and city-level data. It's not GPS-precise, but it's enough to see whether your campaign is reaching the right geographic audience.
Device Type
The user agent string sent by the scanner's browser reveals device information. You can typically see the split between iOS and Android devices, and sometimes the specific browser used. This can inform design decisions-if 90% of your scans come from iPhones, optimise the destination page for Safari on iOS.
Operating System and Browser
More detailed analytics may show the operating system version and browser. This is particularly relevant if your destination page uses features that require newer browser versions. If a significant portion of your audience is on older devices, you may need to ensure backward compatibility.
Unique vs Repeat Scanners
Some platforms attempt to distinguish between first-time and repeat scanners using cookies or device fingerprinting. This is approximate-a person could scan once on their phone and once on a tablet and appear as two unique users. But it provides a rough sense of whether your code is being scanned by new people or the same people repeatedly.
What QR Code Analytics Cannot Tell You
It's important to understand the limitations of QR tracking:
Personal Identity
QR code analytics do not tell you who scanned the code. You don't get names, email addresses, or phone numbers unless the destination page collects that information. The data is anonymous at the individual level.
Precise Location
IP geolocation is not GPS. It's based on the IP address assigned by the internet service provider, which may be miles from the scanner's actual location. Mobile network IPs are particularly imprecise. You'll know the city, but not the street corner.
Offline Context
You know someone scanned your code, but you don't know the context. Did they scan it from a printed flyer, a billboard, or a screen? Did they scan it immediately upon seeing it, or did they photograph it and scan later? This context is lost in the analytics.
Conversion Without Additional Setup
A scan is not a conversion. Someone scanning your code and landing on your page doesn't tell you whether they bought something, signed up, or took any other action. To track conversions, you need to integrate with web analytics or set up conversion tracking on the destination page.
Setting Up QR Code Tracking
If you want trackable QR codes, here's how to approach it:
Choose a Platform with Analytics
Not all QR code generators offer tracking. Free tools often provide only static codes. If tracking is important, look for a platform that explicitly offers dynamic codes with analytics. Features to look for include: real-time scan counting, geographic data, device breakdown, time-based graphs, and export capabilities.
Use UTM Parameters for Campaign Tracking
For integration with Google Analytics or other web analytics platforms, add UTM parameters to your destination URL. A URL like example.com/page?utm_source=print&utm_medium=qr&utm_campaign=spring2026 will appear in your analytics with clear campaign attribution. This lets you compare QR code traffic against other sources and track behavior on your site after the scan.
Create Separate Codes for Different Placements
If you're placing QR codes in multiple locations-a magazine ad, a poster, and a flyer-create separate dynamic codes for each. This lets you compare performance across placements. The destination URL can be the same, but each code will have its own analytics.
Set Up Conversion Goals
If your QR code campaign has a specific objective (purchases, sign-ups, downloads), set up conversion tracking on the destination page. Google Analytics goals, Facebook Pixel events, or other conversion tracking tools will tell you not just how many people scanned, but how many completed the desired action.
Privacy and Compliance Considerations
QR code tracking involves collecting data about users, which raises privacy considerations:
GDPR and Similar Regulations
Under GDPR and similar privacy laws, IP addresses are considered personal data. If you're tracking QR code scans and collecting IP addresses (even for geolocation), you need a legal basis for processing, a privacy policy that discloses the tracking, and potentially user consent. Many QR code platforms offer anonymised tracking options that don't store IP addresses.
Transparency
It's good practice to inform users that scanning the code will take them to a tracked destination. A simple note near the code like "Scan to visit our website" is usually sufficient context. For more detailed tracking, consider a landing page that explains what data is collected.
Data Retention
Consider how long you need to retain scan data. Privacy best practice is to keep data only as long as necessary for the purpose it was collected. Most QR code platforms allow you to set data retention periods or delete historical data.
Alternative Tracking Methods for Static Codes
If you prefer static QR codes (for their simplicity, permanence, and lack of ongoing costs) but still want some tracking capability, there are alternatives:
Google Analytics on the Destination Page
Even without QR-level tracking, you can see traffic to the destination page in Google Analytics. You won't know specifically that visitors came via QR code, but if the page is only accessible via the QR code (a unique URL not linked anywhere else), you can infer that traffic came from scans.
Unique Landing Pages
Create a unique landing page for each QR code placement. A URL like example.com/flyer or example.com/magazine-ad won't be accessed any other way. Traffic to that page equals QR code scans. This works with static codes and requires no special tracking infrastructure.
Custom URL Shorteners
Use a custom URL shortener (like your own domain with a redirect service) to create trackable short URLs, then encode those into static QR codes. This gives you some tracking capability while keeping the QR code itself static. You'll need to run your own redirect service or use a URL shortener with analytics.
Interpreting QR Code Analytics
Once you have tracking data, how do you make sense of it?
Scan Rate
If you know how many people saw your QR code (print run of a magazine, foot traffic past a poster), you can calculate a scan rate: scans divided by impressions. A 1-2% scan rate is common for general placements. Highly relevant placements (like a QR code on product packaging that leads to setup instructions) can see much higher rates.
Time Patterns
Look for patterns in when scans occur. Do they cluster around certain times of day or days of the week? This can tell you about your audience's behavior and inform when to launch campaigns or when to ensure your destination page is performing well.
Geographic Distribution
Are scans coming from where you expected? If you're running a local campaign but seeing scans from other regions, either your placement is reaching further than intended or there's something wrong with the geolocation data. Conversely, if you expected national reach but all scans are from one city, your distribution may be too concentrated.
Device Insights
The device breakdown can inform design decisions. If most scans come from mobile devices (which they typically do), ensure your destination page is mobile-optimised. If you see a surprising number of desktop scans, someone may be photographing your QR code and scanning the photo from a desktop screen later.
Comparison Across Placements
If you have multiple QR codes for the same campaign in different placements, compare their performance. Which placement gets the most scans? Which gets the most unique scanners? This data can inform future decisions about where to invest in QR code placements.
Common Analytics Pitfalls
Counting Scans Instead of People
One person might scan a code multiple times-testing it, showing it to a friend, or returning to the content later. Total scans overstate the number of people reached. Use unique scan counts when available, and remember that even those are approximations.
Ignoring the Funnel
A scan is just the first step. Someone scans, lands on your page, and then... what? If 1,000 people scan but only 10 buy something, the problem isn't the QR code-it's what happens after. Use conversion tracking to understand the full funnel.
Attribution Errors
If someone photographs your QR code and scans it later from the photo, the location and time data will reflect when and where they scanned the photo, not when and where they saw your original code. This is a limitation of the technology that can't be avoided.
VPN and Proxy Effects
If a significant portion of your audience uses VPNs, the geographic data will be distorted. Someone scanning from London via a New York VPN will appear as a US scan. This is increasingly relevant as VPN usage grows.
Best Practices for QR Code Analytics
- Use dynamic codes when tracking is important; static codes when permanence and simplicity matter more.
- Add UTM parameters to destination URLs for integration with web analytics.
- Create separate codes for each placement to enable comparison.
- Set up conversion tracking to measure outcomes, not just scans.
- Review analytics regularly and adjust campaigns based on data.
- Be transparent about tracking and comply with privacy regulations.
- Consider data retention and delete old data when no longer needed.
- Don't over-interpret small sample sizes; wait for statistically significant data.
Frequently Asked Questions
Can you track how many times a QR code is scanned?
Yes, but only with dynamic QR codes. Dynamic codes use a redirect URL, allowing the QR code provider to count scans before sending users to the destination. Static QR codes encode the destination URL directly and cannot be tracked because there's no intermediary server to count the scans.
What information can QR code analytics show?
QR code analytics typically show: total scan count, scans over time (by day/hour), geographic location of scanners (country, city), device type (iOS/Android), browser used, and sometimes the referring source. Advanced analytics may include unique vs repeat scanners and conversion tracking.
Can static QR codes be tracked?
Static QR codes cannot be tracked directly because they encode the destination URL directly into the code. However, you can track activity on the destination page using standard web analytics tools like Google Analytics. You won't know how people arrived at the page, but you can see page visits and behavior.
Is QR code tracking GDPR compliant?
QR code tracking can be GDPR compliant if implemented correctly. The data collected (IP address, device type, location) is considered personal data under GDPR. You need a legitimate basis for processing, a privacy policy disclosing the tracking, and should offer users the ability to opt out. Many QR code platforms offer anonymised tracking options that are more privacy-friendly.
How accurate is QR code location tracking?
QR code location tracking uses IP geolocation, which provides city-level accuracy at best. It cannot pinpoint exact locations like GPS. The accuracy varies depending on the IP database used and how users connect to the internet (mobile networks often show less accurate locations than WiFi). VPNs and proxies can also distort location data.