qrabbit.net

QRcode Tracking: What Scan Stats Tell You and What They Cannot

QRcode tracking only works when a short link sits between the printed code and the destination, so the server sees each scan before sending the person on. This guide covers what scan stats tell you, what they cannot, and how to run a fair test between two placements.

Sophie ParkerPublished · Updated · 7 min read
Two QR codes on a flyer and a poster scanned by phones, each scan counted separately on its way to the destination page
Key takeaways The short version, before the details.
  1. Only a dynamic code can be tracked. A static code holds the destination itself, so no server ever sees the scan.
  2. Each counted scan records a country, a device type, a browser and an operating system. It does not record who scanned, their city or what they did next.
  3. Link previews from chat apps and scripted requests are filtered out, and no IP address is stored with a scan.

How qrcode tracking works

A trackable QR code does not hold your web address. It holds a short link on the QRabbit domain, and that link is what gets printed. When someone scans the code, their phone opens the short link, the server notes the scan and then sends the phone on to wherever the code points today.

That middle step is the whole trick. The scan is logged after the response has gone out, so the person in front of your poster is not kept waiting while the stats are written. If logging ever fails, the code still opens. A printed code never breaks because of tracking.

For a link code the hand-off is an ordinary HTTP 302 redirect. For a hosted landing page, contact card or WiFi code, the short link opens the page itself, and that visit is the scan.

Can a static QR code be tracked?

No. A static code stores the destination directly in its black and white squares. The phone reads the address and goes straight there, so no counting server is ever involved. On QRabbit, static codes are even built inside your browser, which means nothing about them reaches our servers.

That is why dynamic QR code tracking and dynamic codes always come together. The short link is what makes a code editable after printing, and it is also what makes it countable.

QuestionStatic codeDynamic code
What is inside the codeThe destination itselfA short link to QRabbit
Scans countedNoYes
Destination can change after printingNoYes
Needs an accountNoYes

Already printed a static code that points to your own website? You cannot count the scans, but you can still count visits in your own site analytics if the link carried campaign tags (UTM parameters) when you made it. That measures page visits, not scans.

To make a trackable code, pick the editable link option on the URL QR code generator, or build a hosted page with the QR landing page builder, which counts scans the same way.

What QR code scan tracking shows

Every counted scan is stored as a handful of coarse buckets, not raw data. From those, the analytics view builds:

  • Scan totals: all scans in the chosen period, this week compared with last week, and today.
  • A scans over time chart: for today, the last 7, 14 or 30 days, the last 12 months, this month, this year, all time or a custom range. How far back you can look depends on your plan.
  • Top countries: taken from the country our network edge attaches to each request, similar to the country header Cloudflare documents.
  • Devices: mobile, tablet or desktop, read from the User-Agent header the phone sends.
  • Browsers and operating systems: for example Safari, Chrome, Samsung Internet, iOS or Android.
  • Busiest days and time of day: scans per weekday and per part of the day, with times shown in UTC.
  • Top performers: in the overview for all your codes, which ones are scanned most.

Together these answer practical questions. Is the flyer in the café scanned at lunchtime or in the evening? Did the trade show code get scanned abroad? Are your visitors mostly on iPhone, so the page you link to must work well in Safari?

What QR code stats cannot tell you

Scan stats describe scans, not people. Some things they will never show:

  • Who scanned. No name, email, phone number or account is attached to a scan.
  • The city or exact location. The country is the finest level. There is no city or street-level breakdown.
  • Unique people. The total counts scans. One person scanning the same poster on Monday and again on Friday counts twice.
  • What they did next. Once the phone lands on your website, QRabbit is out of the picture. Whether they bought, signed up or left is something your own site or shop analytics has to measure.
  • Where the code was hanging. The stats know which code was scanned, not which wall it was on. That is why one code per placement matters (see below).

Time of day is reported in UTC. If your codes are printed in a city several hours away from UTC, shift the time buckets before drawing conclusions about lunch or evening traffic.

Why bot scans are not counted

Short links get pasted into chats all the time. When that happens, WhatsApp, Slack, Telegram, Discord, LinkedIn and others fetch the link to build a preview card. Those fetches are not people, and counting them would inflate your numbers every time someone shares the code online.

So the scan log treats these as bot hits and leaves them out of every total, chart and breakdown:

  • known link-preview agents and search engine crawlers
  • requests with no User-Agent, or one that is not a browser at all
  • requests that only ask for the headers of a page instead of the page
  • scripted requests missing the headers a real browser sends when it opens a page

Bot hits still open the destination, so previews keep working. They are kept apart, and when there are any, the analytics view tells you how many were filtered out of the numbers. Rapid repeat hits on one code from the same network are also limited, so a script cannot pump up a count.

Is QR code scan tracking private?

The scan record holds only the country, device type, browser and operating system, plus the time. No IP address and no raw User-Agent string are saved with it. The network address is used in the moment for rate limiting and is not written to the scan log.

How to compare two QR code placements

Because a scan only tells you which code was used, the way to compare a flyer with a poster is to give each one its own code. A simple test looks like this:

  1. Create one dynamic code per placement. Point them all at the same page, so the only difference is where they hang.
  2. Name each code after its spot, for example "Flyer, front desk" and "Poster, shop window". Put them in one project to keep the test together.
  3. Print and place them at the same time, at a similar size, so neither gets a head start.
  4. Wait for a full week or two. Weekdays differ, and a few scans prove little.
  5. Read the results. The overview ranks the codes under top performers, and each code has its own chart, countries and devices.

To keep a record or share it with a colleague, export the stats as CSV or PDF, either for one code or for everything in view. The CSV lists the period, total scans, this week and today, top performers, top countries, devices, busiest days and time of day, and opens straight in Excel or any spreadsheet.

Keep the destination identical during the test. If you edit the target of one code halfway through, you are testing two things at once.

Ready to see who scans your codes, and where?

  • An editable link you can change after printing
  • Bot-filtered scan counts by country, device, browser and OS
  • One code per placement, compared side by side and exported as CSV
Create a trackable QR code

Frequently asked questions

Yes, if the code is dynamic. A dynamic code opens a short link first, which counts the scan before sending the phone on. Totals appear per day, week and chosen period, and link previews from chat apps are left out, so the number reflects real people opening the code.

No. A static code stores the destination directly, so the phone goes straight there and no server sees the scan. If the link pointed to your own site with campaign tags, your web analytics can count the visits, but that counts page visits rather than scans.

No. A scan carries no name, email or account. What you see is a country, a device type, a browser, an operating system and the time. No IP address is stored either, so the stats describe how your code is used, not which person used it.

Only down to the country. There is no city or street-level location. To learn which physical spot drives scans, give each placement its own code, for example one on the flyer and one on the poster, and compare their counts.

Create one dynamic code per placement, point them at the same page and name each after its spot. Put them up at the same time, wait a week or two, then compare them in the analytics overview or export the stats as a CSV file.