QR Code Campaign Measurement: Scans to Conversions
Key Takeaway
Measure QR campaigns across redirect scans, UTM-tagged sessions, conversions, cost, and benchmarks. Includes QRLynx plan data and unique-scan logic.
The measurement model
What does a QR campaign measurement plan include?
QR campaign measurement connects a redirect scan, a destination-page visit, and a business outcome. These are related events, but different systems record them and the report should keep them separate.
QRLynx records an eligible dynamic scan after bot filtering and access checks. Your web analytics records the landing-page session. A form, checkout, booking flow, or other destination event records the conversion. A campaign label such as utm_content=front-window gives every layer the same placement name.
This separation matters because a scan can occur without a completed page load, and a page visit can occur without a conversion. A trustworthy report keeps the three counts visible instead of presenting them as one number.
The three layers of QR campaign measurement
Each layer answers a different question. Use all three when the campaign has a lead, booking, or revenue goal.
| Measurement layer | Recorded by | Useful metrics | Question it answers |
|---|---|---|---|
| Scan | QRLynx dynamic redirect | Total scans, daily unique scans, time, geography, device details by plan | Did people interact with this printed code? |
| Destination visit | Your website analytics | Sessions, engaged visits, landing-page behavior, source and campaign | Did the destination load and hold attention? |
| Conversion | Your form, booking, checkout, or CRM | Leads, bookings, purchases, revenue, conversion rate | Did the campaign produce the intended result? |
How dynamic QR scan tracking works
A dynamic QR code stores a short QRLynx-operated redirect URL in the printed symbol. When someone scans, the redirect service loads the saved destination, records the eligible event, and sends the browser to that destination.
The printed redirect stays the same while the owner updates the destination in the dashboard. That makes the code useful for campaigns that need analytics or may need a corrected landing page after printing.
A static QR stores its final payload directly. For a static URL code, the destination website can still record ordinary visits or server requests. A unique tagged URL can make those visits attributable to the placement, but there is no separate platform redirect event. Historical scan events cannot be reconstructed after the fact.
The same redirect model supports standard dynamic URL codes and dynamic GS1 Digital Link QR codes. The GS1 identifier structure remains part of the product URI while QRLynx manages the selected destination and scan analytics.
What QRLynx analytics include by plan
Every plan supports unlimited scans. Analytics history and available breakdowns increase by plan.
| Plan | Active dynamic QR codes | Analytics detail | Campaign tools |
|---|---|---|---|
| Starter | 5 | Counts, charts, top QR codes, timing, and activity across 3 months | Editable destinations and basic AI summaries |
| Starter+ | 50 | Starter analytics across 1 year | Full AI Insights and vector downloads |
| Pro | 300 | Starter analytics plus country detail across 2 years | Smart redirect rules, scheduling, and access controls |
| Business | 1,000 | City, device, operating system, and browser detail across 3 years | CSV export, lead forms, bulk creation, and team workspaces |
| Enterprise | 5,000 | Business analytics detail with no fixed plan lookback cap on available history | Custom redirect domains, retargeting tags, and white-label tools |
What does a unique scan mean in QRLynx?
A QRLynx unique scan is the first observed scan for the same QR code and IP address on a UTC calendar date. Later scans from that combination on the same date count as repeat activity. The next UTC date starts a new daily unique window.
Use unique scans as a daily reach estimate rather than an exact count of people. Several people on one shared network can appear as one daily unique scan, while one person who changes networks can appear more than once. QRLynx shows owners aggregate results rather than scanner IP addresses or personal identity.
Total scans remain useful for engagement intensity. Daily unique scans are better for estimated reach. Reporting both prevents a frequently scanned menu, WiFi card, or product label from looking like a larger audience than it was.
What do QRLynx scan benchmarks show?
QRLynx has processed over 5 million QR code scans through its redirect infrastructure. The 2026 scan benchmarks report publishes three useful planning signals from that dataset:
- Android accounts for about 58% of smartphone scans and iPhone about 42%. Test the destination on both Android Chrome and iPhone Safari before printing.
- About 76% of scans occur Monday through Friday. Compare like-for-like weekday windows when reviewing a campaign.
- Wednesday is the busiest day at about 17% of scans. A midweek peak is a useful reference, but each placement should establish its own baseline.
The QRLynx analytics methodology explains how scan events are collected and how automated traffic is excluded. These figures describe the published QRLynx dataset. They are planning references, not a promised scan rate for a new campaign.
The metrics worth putting in a QR campaign report
A compact report should show interaction, estimated reach, destination performance, and the intended outcome.
| Metric | Calculation | Use | Decision |
|---|---|---|---|
| Total scans | Eligible redirect events | Measures interaction volume | Compare activity over time for the same placement |
| Daily unique scans | First scan per code, IP address, and UTC date | Estimates daily reach | Separate repeat use from broader exposure |
| Landing sessions | UTM-tagged sessions in destination analytics | Measures successful page arrivals | Find load, redirect, or tracking loss |
| Conversion rate | Conversions divided by landing sessions | Measures destination effectiveness | Improve the offer, page, or form |
| Cost per conversion | Placement cost divided by conversions | Measures campaign efficiency | Move budget toward stronger placements |
How to build a QR campaign measurement plan in QRLynx
Define the report before the QR reaches a printer. A small campaign can use QRLynx's free Starter plan, the UTM Builder, and analytics already installed on the destination.
Define the conversion before creating the code
Write down the action that makes the campaign useful: a form submission, booking, purchase, menu view, file download, or another destination event. Confirm that the destination can record it. A scan count without a defined outcome measures interaction, not campaign success.
Give each placement a stable campaign label
Create a separate dynamic QR for each placement or channel you want to compare. Use names such as front-window, table-card, and package-insert. One code can cover identical copies of the same placement when individual-item attribution is unnecessary.
Build the tagged destination URL
Use the QRLynx UTM Builder to add consistent campaign fields. A print example is utm_source=qr, utm_medium=print, utm_campaign=summer-menu, and utm_content=table-card. Google Analytics documents how UTM parameters populate campaign reports.
Create and test the dynamic QR code
Open the QRLynx QR code generator, select the URL QR type, paste the tagged destination, and save it in dynamic mode. Download the final design, then scan both the file and a physical proof at the intended size. Confirm the destination, UTM values, and conversion event before approving the print run.
Review the complete funnel on a consistent schedule
Read QRLynx for total and daily unique scans, destination analytics for tagged sessions, and the destination system for conversions. Compare the same placement over equivalent time windows. Keep the placement label identical across reports so the funnel can be joined without guesswork.
Measurement plan ready?
Create and test your measurable QR campaign
Give the placement its own QRLynx dynamic URL QR, use a consistent campaign label, and verify the full scan-to-conversion path before printing.
Common QR tracking mistakes
Most tracking problems start before the first scan. The fix is a clear measurement plan and consistent labels.
Using one QR across unrelated placements
A shared code gives one total for every poster, package, table, or event. Create separate codes for the placements that need separate decisions.
Sending traffic to an untagged destination
The dynamic dashboard can count scans, but the destination analytics needs campaign parameters to group the resulting sessions. Build and test the UTM-tagged URL before saving the code.
Reporting total scans as people
Total scans include repeat use. Pair total scans with QRLynx daily unique scans, and describe the latter as an estimate rather than an exact person count.
Stopping the report at the redirect
A scan is the start of the funnel. Add the destination visit and defined conversion so the report can show where attention becomes a useful outcome.
Comparing unlike time windows or placements
A table card, package insert, and roadside sign have different exposure and dwell time. Compare a placement with its own history or a closely matched test, using equivalent days and distribution.
Testing only the image on a screen
Tracking succeeds only if the printed code scans. Test the final size, material, lighting, distance, and destination flow before production.
How should QR analytics handle privacy?
QR analytics should collect and present only the data needed for the campaign. QRLynx gives code owners aggregate scan results rather than scanner identity or IP addresses. Infrastructure processing uses request data for functions such as daily unique-scan estimation, geographic aggregation, security, and abuse prevention.
IP addresses and other online identifiers can be personal data under the EU General Data Protection Regulation. Campaign owners should describe destination tracking, choose an appropriate legal basis, limit retention to what they need, and request consent where their forms, advertising tags, or local rules require it.
Do not place names, email addresses, account numbers, or other personal data in UTM values. Google Analytics specifically prohibits sending personally identifiable information and recommends keeping it out of campaign parameters. QRLynx provides privacy controls that support GDPR workflows, while the destination website, form, analytics platform, and advertising configuration remain part of the campaign owner's compliance assessment.
QR campaign measurement FAQ
Direct answers about scan events, destination sessions, UTMs, analytics tiers, privacy, and conversion reporting.
Can I track scans on a static QR code?
A static QR code goes directly to its payload, so a QR platform has no redirect event to count. A static URL can still send visitors to a unique UTM-tagged page that your website analytics measures. That produces destination visits, not a separate scan record. Existing website analytics or server logs may show visits to an already printed destination, while past QR scan events cannot be recreated.
What QR analytics are included on the free plan?
Starter includes 5 active dynamic QR codes, unlimited scans, and 3 months of scan counts, timing, and activity history. A registered Starter account also gets watermark-free downloads and editable destinations.
How does QRLynx calculate a unique scan?
The first scan for the same QR code and IP address on a UTC date is marked unique. Later scans for that combination on the same date are repeat activity. Use the result as a daily reach estimate because shared networks can group several people and network changes can split one person across more than one estimate.
Why do QRLynx scans and Google Analytics sessions differ?
QRLynx counts eligible redirect events, while Google Analytics counts destination activity after its tag loads. A person may close the page before the tag runs, block analytics, pass through another redirect, or trigger more than one page event after a single scan. Compare the trend and investigate material changes instead of expecting the two systems to be identical.
Which UTM parameters should I use for a QR code?
Start with utm_source=qr, a medium that describes the material such as utm_medium=print, a stable campaign name in utm_campaign, and the placement in utm_content. Keep spelling and capitalization consistent. The QRLynx UTM Builder creates the final URL.
How do I know which QR placement drove a conversion?
Create a separate dynamic QR for each placement you want to compare, then use the same placement value in the code name and utm_content. QRLynx reports scans by code. The destination analytics and conversion system report sessions and outcomes with the matching UTM value.
What location and device data can I see?
The free Starter plan shows counts, charts, top QR codes, timing, and activity across 3 months. Starter+ extends the history window to 1 year. Pro extends it to 2 years and adds country detail. Business extends it to 3 years and adds city, device, operating system, browser, and CSV export. Enterprise has no fixed plan lookback cap on available analytics history.
Are QR scan analytics GDPR compliant?
Compliance depends on the complete campaign, jurisdiction, purpose, disclosures, and destination tracking. QRLynx provides privacy controls that support GDPR workflows and shows owners aggregate results rather than IP addresses. Campaign owners should assess the destination website, forms, analytics tags, advertising tags, legal basis, and consent requirements.
Can I change a tracked QR destination after printing?
Yes. A saved dynamic QR code keeps the same printed redirect while its owner updates the destination in QRLynx. The existing print continues to resolve through the same code, so its scan history remains attached to that QR.
Do I need a CRM to measure QR conversions?
A small campaign can measure scans, tagged destination sessions, and web conversions with QRLynx plus its existing site analytics. A CRM becomes useful when the result is a lead that moves through later stages or when revenue needs to remain connected to the original placement.
What should a QR campaign report include?
Report total scans, daily unique scans, tagged landing sessions, conversions, conversion rate, and placement cost. Add cost per conversion when the spend is known. Keep each placement on its own row so the report leads to a printing or budget decision.
Sources and methodology
This guide uses current QRLynx product behavior and plan entitlements for every platform claim. First-party benchmark figures come from the QRLynx 2026 scan benchmarks report, with collection and exclusion rules documented on the analytics methodology page.
- Google Analytics: collect campaign data with custom URLs
- Regulation (EU) 2016/679, General Data Protection Regulation
- Google Analytics: avoid sending personally identifiable information
Generic scan-rate percentages are intentionally omitted. Campaign performance depends on exposure, placement, audience, offer, print quality, and destination experience. Establish a baseline from the actual placement and compare equivalent periods.
Continue building the measurement workflow
Use the QR scan tracking setup guide for dashboard fields, location and device reporting, and UTM configuration. Use this measurement guide to join those scan records with destination sessions, conversions, cost, and benchmarks.
