How to Track QR Code Scans: Counts, Sources and Limits

You can track QR code scans when the code opens a web link that records activity. Use the results to compare placements and decide what to improve, while keeping scan counts separate from people and sales. This guide explains the options and walks through a first check with QRown Statistics.

Can you track QR code scans?

Yes, when someone opens a web link from the code and the redirect service or destination website records that request. The printed QR pattern does not send a signal on its own. A camera recognizing it without opening the link leaves no web activity to count.

Can you tell who scanned a QR code?

No. A standard QR scan does not identify the person or reveal their name or email. Dynamic QR systems can record scan and engagement metadata when someone opens the encoded link. That tells you about activity, not who the person is. A visitor can choose to identify themselves by submitting contact details through a lead form.

QRown Statistics reports recorded scans and profile activity. Sessions group related events; they are not unique people. One person can return in multiple sessions or use multiple devices, and a shared device does not necessarily represent one person.

How QR tracking works: static and dynamic codes

A QR code stores data, often a URL. Merely pointing a camera at the printed pattern does not notify QRown. Tracking happens when the browser requests the link. QRown codes open a managed redirect, which can record the QR source before sending the visitor to the destination.

A static code contains its destination directly. If it encodes a website URL, that website can measure visits, but cannot automatically distinguish a QR visit from other visits to the same URL. A static code containing only contact details has no web request to count. You cannot add QRown scan history retroactively to an unrelated printed code.

A dynamic code uses a managed link so the destination behind it can change. The printed pattern still stays the same. QRown's main profile QR always opens your profile, whose content you can update. Additional codes can use editable external destinations. See QR codes and contact cards for the sharing workflow and plan allowances before planning multiple sources.

For help choosing between a direct destination and a managed redirect, read the static vs dynamic QR code comparison.

Can you see how many times a QR code was scanned?

You can see how many scan events were recorded for the code in your reporting period. In QRown, the scan total counts requests to the managed QR link after reporting filters. Opening a copied QR link can also create a scan event: the request does not prove that someone used a camera or stood beside the original print.

For example, one visitor opening the same QR link three times can contribute three scans. That does not establish three people. A scan and the profile view that follows are separate events, while an external destination can produce a scan without a QRown profile view. Do not add those counts together as a visitor total.

If you call this “tracking QR code clicks,” distinguish opening the QR link from clicking a link on the page it opens. QRown reports those as separate actions. Owner and authorized team self-interactions are suppressed; sessions identified as bots are excluded from Statistics.

How to track a QR code in QRown: a first check

Use a profile you control and record the time of your test. This checks the reporting path before you spend money distributing a code; it is not a campaign result.

1. Choose the profile and QR code. Select QR in the profile navigation to open QR Codes. Its main code opens that profile. If your plan allows additional codes, use Create QR Code and give the new source a descriptive title, such as “Front window.” Check its destination before sharing it.
2. Use the actual QR image. Open the code's More actions menu and choose Download PNG. Print a proof or display the image on a second screen. Typing the profile's @handle URL directly tests a profile visit, not a QR scan.
3. Open the scan link as a visitor. Use a fresh private browser session or a device/browser that has not signed in to the owning account. Accept the camera's link prompt and let the destination load. Signing out alone may leave a browser identifier that still suppresses your own activity.
4. Try one action on the profile. For example, open a website link you control or download the contact card. Write down what you did. A download records the request for the file, not whether you imported it.
5. Return to Statistics. In your signed-in browser, select Stats on the same profile, then Overview. Choose a date range containing the test and refresh the page. Look at QR scans and the relevant action total. Live visitor activity can also change those totals.
6. Inspect the detail your plan includes. Use Sources to find the QR title, Actions for action breakdowns, and Activity for recorded events grouped by session. In Activity, select a range that includes the test and use Refresh activity.

The reporting time zone appears in Statistics. Use the same range and time zone when comparing results. An external QR destination can produce a scan without a QRown profile view or profile action.

Which Statistics reports can you use?

Overview provides performance totals. Sources and Actions add breakdowns; Activity shows recorded session activity. The table below follows QRown's current plan allowances. For a team profile, access follows the workspace owner's plan and your permissions.

These are reporting access limits, not a promise that data is deleted when a period leaves your available range. Additional QR codes, lead features and third-party Analytics have their own allowances on the pricing page.

What information can QRown measure from QR code activity?

Choose a business question before comparing numbers. “Are people scanning our reception sign?” needs a different test from “Does this flyer bring enquiries?”

• QR scans: Is the printed invitation getting a response?
• Sources and sessions: Which QR codes generated recorded activity, and which events belong to the same session?
• Referrers and devices: What context is available about the visit? Referrers may be missing, and device information does not identify a person.
• Profile views: Is the destination receiving visits, including visits through other channels?
• Contact and link actions: What are visitors trying to do on the page?
• Contact-card downloads: Are people requesting a copy of your details?
• Lead submissions: Are visitors actively asking you to follow up?
• Content and payment actions: Which blocks draw interaction? Payment clicks and selected amounts show intent, not completed payments or revenue.

These are recorded events and session context, not exact counts of unique scanners.

A click on a booking link is not a confirmed appointment. A download is not a confirmed saved contact. Check bookings and sales in the systems that actually complete those actions.

QR code scan tracking vs website analytics

Scan tracking answers which QR link received requests. Website analytics describes activity recorded on the destination website. If a QRown code redirects to your own website, QRown can count that redirect scan; measuring subsequent activity there requires reporting on that website.

A static QR linking directly to your website can still support campaign measurement. If you use Google Analytics, campaign parameters such as utm_source, utm_medium and utm_campaign label traffic in its reports. Choose a distinct tagged destination for each placement before printing. Those labels describe the link used; they do not prove where someone was when they opened a copied or shared URL.

Keep each tool's numbers labeled. QR requests, page views and sessions measure different things, so their totals need not match. Align the reporting period and time zone before comparing them, then check what each report includes and excludes.

In QRown, Statistics is first-party reporting, Metrics are calculated values, and Analytics means third-party integrations. You do not need to add an Analytics integration to use built-in Statistics. Read the Google Analytics and Microsoft Clarity setup guide if you need a supported Business integration on your QRown profile.

Give each placement a separate source

If the same QR image is printed on both a window sign and a flyer, its scan total cannot tell you which object was scanned. To compare placements, use separate QR codes and label them clearly, such as “Front window” and “Market flyer.” Additional QR-code allowances depend on your plan.

QRown records QR sources by their code identity. Print Studio designs also have their own QR identities, grouped by product type in reporting. Printing two copies of one design does not create two independently measurable locations.

1. Choose two placements you can compare fairly and create a separate code for each.
2. Keep the offer and destination consistent while testing the placement.
3. Record the distribution dates, quantities and costs in your own campaign notes.
4. Review the same date range in Statistics and compare the recorded sources.

A source identifies the QR code, not the scanner's physical location. Use a separate code for each shop, sign or placement you want to compare, and keep a record of where you used it.

Worked example: what two scan counts tell you

Illustrative numbers, not customer results: suppose “Front window” records 120 scans and “Market flyer” records 60 in the same period. The window code received twice as many recorded scan requests. That does not establish twice as many people, better lead quality or a better return on the printing cost.

If the profile also records 12 lead submissions, you cannot divide 12 by 180 and call it a scan-to-lead conversion rate. The totals can include repeat scans and leads arriving through other channels. Review the context attached to each enquiry where available; keep it separate from the independent scan totals.

Before deciding where to print more, compare the time each placement was available, the number distributed and the enquiries you actually followed up. If you do not know exposure, report the scan counts without inventing a response rate.

Turn the pattern into the next test

• Few scans: Check visibility, lighting, code readability and whether the printed invitation gives a reason to scan.
• Visits but little action: Make the promised information easy to find. Move the relevant contact or link action higher.
• Useful enquiries from one source: Review their quality and your follow-up before expanding that placement.
• More scans but no useful enquiries: The offer may attract curiosity without the kind of interest you need.

Compare similar periods and exposure. A flyer distributed widely may produce more scans than a small sign without being the better investment. Scan totals alone do not supply a response rate; you need a meaningful distribution or exposure estimate too.

See what preceded an enquiry

A lead form gives visitors a way to tell you what they need. In the Leads Inbox, Lead Story can show recorded context associated with a submission, such as the arrival source and activity in its session. This context does not tell you the scanner's physical location.

Read that context alongside what the person actually submitted. Add your notes, respond through your email app where available, and update the lead's status as you follow up. Available lead fields, submission visibility and follow-up features vary by plan.

Why is a test scan missing or different from the total you expected?

First separate readability from reporting. Use the physical print-test checklist if a camera struggles to recognize the pattern. A failed recognition cannot generate a request for Statistics to count.

• The camera only recognized the pattern. Open the suggested link; detection by itself makes no request to QRown.
• You used the profile URL or another provider's QR. Test the QR image downloaded from this profile. A direct visit does not become a QRown scan.
• The browser belongs to you or an authorized teammate. Use a fresh visitor browser for the check. QRown suppresses owner and authorized team self-interactions.
• The report has a different scope. Confirm the profile, date range and reporting time zone, then refresh. A locked tab is a plan restriction, not evidence of zero activity.
• The code is retired or the destination is inaccessible. Follow the scan all the way through. A retired code opens an inactive-code notice and does not record a new scan. A Private profile cannot serve as a visitor-facing destination.
• Requests are not unique people. Reopening a QR link can add scans. Recognized bot sessions are excluded from Statistics, but bot filtering cannot guarantee that every remaining request came from a person.

Know what the data leaves out

Repeat activity can come from the same person. Owner and authorized team self-interactions are suppressed, so your own testing may not appear in Statistics. Device, session and source information can be incomplete. Treat the report as recorded evidence, not a complete count of people exposed to your material.

The main profile QR always opens your QRown profile. Additional codes can send people to an external destination; QRown can record that redirect scan, but it does not thereby measure everything that happens on the external site. Changing a destination also does not turn Statistics into a report of historical destination versions.

Put tracking to work on your next placement

Start with the guide that matches what you plan to share, then use the same tracking check before distribution.

• Add a QR code to a business card and choose a useful destination for a new contact.
• Plan a storefront QR code with a clear invitation for walk-up and after-hours visitors.
• Choose a QR marketing experiment for flyers, counters or events, and keep a record of the offer and distribution.

Ready to try it? Create a QRown profile, share its QR code, and check the recorded activity after visitors use it.