What website visitor statistics show
QREasy website visitor statistics record visits to a hosted website created with the small website builder. They are useful for observing activity around the site, but a visit is not automatically a scan of a printed QR code. A visitor may have arrived through a static URL QR, a dynamic QR, or an ordinary link, so the presence of a visit does not by itself reveal its source.
Treat each number as the specific measurement it represents. Website analytics answer how many hosted-site visits were recorded; dynamic QR analytics answer how many dynamic-code scans were recorded. These figures can be read together, but they are not interchangeable. For the wider product context, see information about QREasy, which covers its digital business cards for Apple Wallet and Google Wallet, small website builder, and free QR tools.
Website visits versus dynamic QR scans
A website visit is an activity recorded for the hosted website. A dynamic QR scan is a separate recorded event involving a dynamic code and its managed redirect. Seeing a scan and a later website visit does not automatically mean that the scan produced the visit, or that the visit came from a scan. The destination configured for the code and the available analytics window must be checked before connecting the two records.
This distinction prevents a common category error. A static URL QR may point to the same hosted website, yet its use does not automatically create a static-code scan record. Conversely, a dynamic QR can redirect somewhere other than the website, so a scan may exist without a website visit following it. Never add the totals as if they represented different people.
If you need to change where a dynamic QR sends people repeatedly, the step-by-step guide to creating a dynamic QR in QREasy explains the workflow. The managed destination can change without reprinting the code, subject to plan limits. If the URL stays fixed and only content at that URL changes, a static URL QR can remain in use.
How visits are recorded regardless of source
Website visits are recorded independently from the traffic source. A visitor can reach the hosted site through a static URL QR, a dynamic QR, or a normal link, and the site can still record the visit in each case. A dynamic QR is therefore not required to measure website visits: the hosted site supplies that measurement, while a dynamic QR adds a separately tracked redirect.
The practical implication is that you should not infer a source from a website visit alone. Before attributing activity to a campaign, check for a corresponding dynamic scan, verify the code's destination, and confirm that the dates fall within the stored history. If those records do not establish the route, report a recorded website visit rather than a proven campaign visit.
To illustrate, consider reading a single business's dynamic scan history alongside its hosted page visits: this shows why the two views belong side by side. A scan count describes recorded dynamic scans; a visit count describes recorded hosted-site visits. Neither figure alone supplies a complete visitor journey.
Why static QR codes do not report scans
A static URL QR encodes one fixed URL. The content served at that URL can still change without changing or reprinting the code. A hosted webpage can be replaced with new material, or a PDF can be replaced at the same address. Only changing the encoded URL itself requires a new static QR. This differs from embedded static vCard data, where the contact payload is part of the code rather than a separate URL.
Static QR codes themselves do not report scans. QREasy can provide unlimited static QR codes, but that does not mean unlimited static-code scan tracking. For a separate scan measurement, use a dynamic QR with a managed redirect and consult its dynamic scan analytics. The QREasy QR code generators can help you choose between a fixed link, a changing destination, and a digital contact card.
A hosted website also does not require a dynamic QR merely to edit its content; the content can be updated at the same URL. Neither QR type guarantees a scan on every device. Treat recorded scans as the available measurement, not as proof that everyone who saw a code scanned it or completed the next action.
Analytics history across QREasy plans
Analytics history is plan-dependent, so compare only periods that the plan retains. Website visits and dynamic QR scans remain separate measurements within the available window.
- Free: 7 days of analytics history; 1 website with up to 1 page; 1 dynamic QR code; unlimited static QR codes. Contact Wallet cards are included. Website-linked Wallet cards require Lite SME or Business. Price: EUR 0.00 monthly or EUR 0.00 annually.
- Lite SME: 90 days of analytics history; 3 websites with up to 4 pages each; 50 dynamic QR codes; unlimited static QR codes. Website-linked Wallet cards are included. Price: EUR 2.99 monthly or EUR 28.70 annually.
- Business: 90 days of analytics history; 33 websites with up to 10 pages each; 357 dynamic QR codes; unlimited static QR codes. Website-linked Wallet cards are included. Price: EUR 9.99 monthly or EUR 95.90 annually.
What analytics cannot prove
Analytics do not identify everyone who scans a QR code, prove that a particular visit caused a sale, or guarantee leads. They show recorded activity within the available history. This is not a reason to ignore the data; it is a reason to describe it accurately and combine it with other relevant evidence, such as inquiries, bookings, or transactions, when those records are available.
The practical guide to what QR code statistics can actually measure offers a useful framing: separate the metric, source, and action before comparing results. A dynamic scan count and a hosted-site visit count are concrete records, but neither establishes a unique individual, a complete journey, or commercial causation on its own.
When reporting results, name the measurement and period: dynamic QR scans over the last 7 or 90 days, or hosted website visits over the same window. Do not call a website visit a scan, add the two totals as though they represent different people, or claim that a code caused revenue without supporting records. Clear labels keep a simple activity count from becoming a misleading success story.
