QR code analytics transform QR codes from simple links into measurable marketing assets. Without analytics, you know only that a QR code exists — not whether it drives results. With proper analytics setup, every scan becomes a data point: where was the scanner, what device did they use, what time did they scan, and crucially, did they convert after scanning? This guide covers the complete analytics setup process for any QR code deployment. See also our QR code marketing guide for campaign strategy and our QR code tracking guide for step-by-step technical setup.
What QR Code Analytics Measure
Platform-Level Metrics
Dynamic QR code platforms track scans at the redirect server level — every time someone scans your code and is redirected to the destination, the platform logs the event. Standard platform analytics include: total scans (every scan event), unique scans (first scan per device), scan location (city and country, GPS on enterprise plans), device type (iOS vs Android, browser), scan time (hour, day of week, date range), and operating system breakdown. These metrics are available directly in your QR platform dashboard without any additional configuration.
Web Analytics Metrics
Platform scan data captures the scanning event but not what happens afterward on your website. Web analytics (Google Analytics 4) captures the post-scan behavior: time on page, pages visited, conversion actions completed, and revenue generated. The connection between platform scan data and GA4 web behavior data is made through UTM parameters — query string additions to your destination URL that GA4 uses to attribute traffic to specific sources, campaigns, and placements.
Setting Up Three-Layer QR Analytics
- Choose a dynamic QR platform with analytics. Static codes cannot be tracked at the platform level. Select a dynamic QR platform (QR Tiger, Beaconstac, Scanova) that logs scan events. Review the analytics dashboard to understand available metrics before committing to a platform.
- Build your UTM parameter framework. Define consistent UTM parameter conventions before generating any codes. Example: utm_source=direct-mail, utm_medium=qr-code, utm_campaign=spring-2026, utm_content=postcard-a. Document these conventions so all team members use them consistently. Inconsistent UTM naming creates fragmented, difficult-to-analyze data in GA4.
- Append UTM parameters to every destination URL. The complete destination URL encoded in each QR code should include the full UTM string. Use Google's Campaign URL Builder tool to generate properly formatted URLs without manual string construction errors.
- Configure GA4 for QR traffic analysis. In GA4, create a custom channel grouping that identifies "qr-code" as the utm_medium for QR traffic. Create Explorations reports with QR-specific dimensions and metrics. Set up Conversion events for the actions you want to attribute to QR-originated sessions.
- Link platform analytics to GA4 data. Compare scan counts in your QR platform against GA4 sessions with matching UTM parameters. A significant discrepancy (greater than 15%) indicates configuration issues: UTM parameters not encoding correctly, bot traffic filtering, or destination URL redirect errors that strip UTM parameters.
UTM Parameters for QR Codes
Parameter Convention Best Practices
Consistent UTM conventions are essential for clean analytics data. Use lowercase only (UTMs are case-sensitive — "QR-Code" and "qr-code" appear as separate entries in GA4). Use hyphens rather than underscores or spaces. Keep values descriptive but concise. Define a maximum of 5 distinct utm_source values for any campaign to keep reporting manageable. Document your convention in a shared team spreadsheet before launch. Standard QR marketing conventions: utm_medium always equals "qr-code," utm_source identifies the physical placement (flyer, packaging, billboard-houston), utm_campaign identifies the campaign name, utm_content identifies the specific creative variant.
| UTM Parameter | Purpose | QR Example |
|---|---|---|
| utm_source | Physical placement location | lobby-flyer, product-box, trade-show-booth |
| utm_medium | Channel type (always same) | qr-code |
| utm_campaign | Campaign identifier | spring-promo-2026 |
| utm_content | Creative variant or version | version-a, red-cta, photo-variant |
| utm_term | Optional keyword (rarely used) | contactless-menu, scan-to-pay |
Google Analytics 4 QR Code Reporting
In GA4, QR code traffic appears under Reports > Acquisition > Traffic Acquisition when you filter by Session medium equal to "qr-code." Create a custom Exploration report with dimensions: Session source/medium, Session campaign, Session content. Include metrics: Sessions, Engaged Sessions, Conversions, Revenue. This report shows which QR code placement (source), campaign, and creative variant drove the most valuable traffic. Save this exploration as a template to use for all future QR campaigns. GA4's Conversion events should be configured for every key action: purchase completion, form submission, video play, and any other desired QR campaign outcome. Our detailed QR tracking guide covers the complete GA4 configuration process step by step.
Key QR Analytics Metrics and KPIs
Engagement Metrics
Scan rate: Total scans divided by estimated exposures (print circulation, event attendance, etc.). This is your QR equivalent of click-through rate. Benchmark: 1-3% for print, 8-15% for packaging. Unique scan rate: Unique scans divided by total scans. High ratios (greater than 80%) indicate one-time engagement; low ratios (below 50%) suggest repeat engagement behavior worth investigating. Peak scan time: The hour and day of week with the highest scan volume — reveals when your audience is most likely to engage with your physical marketing.
Conversion Metrics
Scan-to-session rate: GA4 sessions from QR divided by platform scan count. Should be 85-95%; lower rates indicate UTM stripping or redirect errors. QR conversion rate: GA4 conversions from QR sessions divided by QR sessions. Compare against your overall site conversion rate to assess QR traffic quality. Revenue per scan: Total revenue attributed to QR sessions divided by total scans. This metric directly supports ROI calculation and placement value comparison.
QR Platform Analytics Features Compared
Analytics depth varies significantly across QR platforms. QR Tiger: Solid analytics including location, device, time patterns, and scan history. Advanced plan adds GPS location and retargeting pixels. Exports to CSV. Beaconstac: Most comprehensive analytics including real-time data, GPS coordinates, device fingerprinting, and direct Google Analytics integration. API access for custom reporting. Scanova: Good analytics dashboard with campaign comparison features. Export to CSV and PDF reports. QR Code Monkey: Free plan has no analytics; paid plan adds basic scan counts and location data. GoQR.me: No analytics on any plan — suitable only for static code generation where tracking is not needed.
Using QR Analytics Data to Optimize
Placement Optimization
Compare scan rates across all placements in a campaign to identify highest-performing locations. If your lobby flyer QR achieves 5% scan rate while your window QR achieves 1.2%, reallocate budget toward lobby materials. Geographic scan concentration can reveal unexpected audience clusters — a fitness brand discovering high scan rates in a specific city may warrant targeted local campaigns. Device type breakdown informs landing page optimization: if 85% of QR scanners use iOS, prioritize iPhone rendering in your landing page testing.
Time-Based Optimization
Peak scan time data informs content scheduling for dynamic QR destinations. If analytics show 78% of scans occur between 11 AM and 2 PM (suggesting lunch-period engagement), optimize the linked landing page for that context — perhaps featuring lunch specials or time-limited midday offers. For restaurant QR menus, scan volume by time of day directly maps to service period traffic, informing staff scheduling decisions.
Calculating QR Code ROI
QR code ROI calculation follows a straightforward formula: (Revenue Attributed to QR - Total QR Campaign Cost) divided by Total QR Campaign Cost, multiplied by 100. Revenue attribution comes from GA4 conversion data filtered to qr-code medium. Total campaign cost includes the QR platform subscription, any design costs for branded codes, and the print production cost of materials where QR codes appear. For non-revenue campaigns (lead generation, downloads), calculate cost per QR conversion and compare against other channel acquisition costs. A business generating $15,000 in QR-attributed sales from a $2,000 campaign (platform + design + print) achieves 650% ROI — a calculation that was previously impossible without QR code tracking.
Analytics data from QR platforms reflects scan events, not website visits. A 10% gap between platform scans and GA4 sessions is normal due to bot filtering, caching, and redirect timing. Gaps exceeding 20% warrant investigation: check that UTM parameters are correctly appended and that destination URL redirects do not strip query strings.
Frequently Asked Questions About QR Code Analytics
How do I track QR code scans?
Track QR scans using a dynamic QR code generator with built-in analytics (QR Tiger, Beaconstac). Supplement platform data with UTM parameters in destination URLs so scans appear in Google Analytics. Set up conversion events to track post-scan actions. This three-layer approach provides complete visibility from scan to conversion.
Can Google Analytics track QR codes?
Google Analytics cannot track QR scans directly, but tracks the resulting web traffic when UTM parameters are appended to QR destination URLs. Use utm_source, utm_medium=qr-code, utm_campaign, and utm_content parameters. These appear in GA4 under Acquisition reports, attributing website traffic and conversions to specific QR code placements.
What data can QR code analytics provide?
QR analytics provide: total scans, unique scans, repeat scan rate, geographic location (city and country), device type (iOS vs Android), browser, scan time (hour, day, week), and referral patterns. Advanced platforms add GPS coordinates, campaign comparison, and conversion rate tracking when integrated with web analytics.
How do I add UTM parameters to a QR code?
Append UTM parameters to your destination URL before encoding it in the QR code. Example: https://yoursite.com/page?utm_source=flyer&utm_medium=qr-code&utm_campaign=spring2026. This full URL gets encoded into the QR code so every scan registers as tagged traffic in Google Analytics.
What is a good QR code scan rate?
Good scan rates depend on placement context. Print advertising: 1-3% of circulation is strong. Direct mail: 3-6% is excellent. Product packaging: 8-15% from purchasers is typical. Event signage: 15-35% of passerby traffic with a compelling CTA. Benchmark against your own previous campaigns for most meaningful optimization insight.
How do I measure QR code ROI?
Measure QR ROI by calculating total revenue attributed to QR-originated sessions (from GA4 conversion data) divided by total campaign cost (platform + production + design). Track the full attribution chain: scans to landing page visits to conversions to revenue. Compare cost per QR conversion against other marketing channel costs.
Do free QR code generators have analytics?
Free QR generators typically do not include scan analytics. Static codes cannot be tracked at all. To access scan analytics, you need a dynamic QR code from a platform that tracks scans through its redirect server. Most paid plans starting at $7/month include basic scan analytics dashboards.
Can I track QR code scans by location?
Yes. Most dynamic QR platforms track scan location at city and country level. Enterprise platforms like Beaconstac provide GPS-level location data for granular geographic analysis. Location data is particularly valuable for multi-location businesses comparing QR performance across different sites or regions.
How do I A/B test QR codes?
A/B test QR codes by creating two codes pointing to different landing page versions and splitting placement equally between them. Measure conversion rates for each over the same time period. Advanced platforms allow destination rotation so a single QR code alternates between two URLs, enabling A/B testing from one physical code placement.
What is the difference between total scans and unique scans?
Total scans counts every scan event, including multiple scans by the same device. Unique scans counts only the first scan from each unique device within a defined period. The ratio between total and unique scans indicates repeat engagement behavior — useful for understanding whether your QR audience returns for multiple interactions.
🔑 Key Takeaways
- Three-layer analytics (platform scans + UTM parameters + GA4 conversion tracking) provides complete QR campaign attribution
- Always use lowercase, hyphenated UTM values and document conventions before launch to maintain data cleanliness
- Platform analytics track the scan event; GA4 tracks post-scan behavior — both are required for full measurement
- Scan-to-session rate should be 85-95%; gaps exceeding 20% indicate UTM stripping or redirect configuration errors
- Compare scan rates per placement to reallocate budget toward highest-performing physical locations
- Peak scan time data enables dynamic QR destination optimization for time-relevant content
- QR ROI = (Revenue Attributed to QR - Campaign Cost) / Campaign Cost — previously impossible to calculate from print