What website visitor statistics actually mean
QREasy provides a small website builder, free QR tools, and digital business cards for Apple Wallet and Google Wallet. A supported Wallet journey can let a recipient review and save contact details or open a website created with QREasy. When that hosted page is accessed, the visit belongs to website analytics; a scan of a managed dynamic code belongs to dynamic QR scan analytics.
These records stay separate even when the same journey continues. For example, scanning a dynamic code can be followed by a visit to its hosted destination, producing one QR scan event and one website visit event. They should not be added together as though they counted different people, nor should one be presented as proof of the other. For product context, see how QREasy brings websites, Wallet cards, and QR tools together.
Instead, use each dataset for a precise question: Did a hosted page receive an access, and did a particular managed code receive a scan? That framing prevents a total from mixing traffic with code interaction and keeps the analysis useful when campaigns, destinations, and time periods change.
- Website visit: access to a page on a QREasy-hosted website.
- Dynamic QR scan: an interaction with a QREasy-managed dynamic code.
- Combined journey: the scan and later visit remain two separate observations.
Visits and dynamic QR scans answer different questions
A dynamic QR code uses a managed redirect. Its destination can be changed without changing or reprinting the physical code, subject to plan limits. That makes it useful when several offline or printed placements should lead to a destination you may revise later. The scan of the managed code is recorded as a dynamic QR scan, not as a website visit.
Neither type of QR code guarantees that every device will scan it. A failed scan can therefore prevent a website visit from occurring, but it does not make the two records interchangeable. If the code leads onward to a QREasy-hosted page, the redirect event and the page access can both describe one journey while remaining distinct measurements.
- Use QR scans to assess interaction with a managed code.
- Use website visits to assess access to a hosted destination.
- Do not use either metric alone to claim that a sale, lead, or specific person was confirmed.
Count website visits regardless of the access route
Website visits do not depend on using a dynamic code. QREasy can record visits to a hosted website whether a visitor arrives through a static URL QR, a dynamic QR, or an ordinary link. A dynamic QR is therefore optional for measuring website access; what changes is whether the code itself can contribute a separate scan statistic.
Access route should still be documented. A static code points directly to a fixed URL, a dynamic code passes through a managed redirect, and an ordinary link skips both. A supported Wallet journey may also open a QREasy-created website, while website-linked Wallet cards require Lite SME or Business. When a dedicated destination is useful, reviewing website templates for different business starts can also make the hosted destination clearer to visitors.
- Static URL QR: the destination may generate a visit, but the code does not.
- Dynamic QR: the code can generate a scan and the destination can generate a visit.
- Ordinary link: it can generate a website visit without involving either QR measurement.
Why static QR codes have no scan statistics
A static URL QR encodes one fixed address. It is not the same as a QR code containing embedded static vCard data. The content served at the address can still change without changing the code: a hosted webpage can be replaced, or a PDF can be swapped for another PDF at the same URL. Only changing the encoded URL itself requires a new static QR code.
Because there is no managed redirect layer in the static route, the code itself does not report scans. This is not the same as saying that its destination receives no traffic. A QREasy-hosted destination can record the visit that follows, while the absence of a static-code scan figure remains intentional. Use the QREasy QR code generators to create a static or dynamic route with that distinction in mind.
- Keep the same URL when only the hosted content changes.
- Create a new static code when the encoded address changes.
- Do not expect a static-code scan total from QREasy analytics.
Analytics history, interpretation limits, and next steps
Analytics history is plan-dependent. Free includes 7 days of history for website visits and dynamic QR scans. Lite SME and Business each include 90 days. Because the measurements remain separate, checking one does not expand or validate the other, and any comparison must respect the shorter window available in the plan.
The limits are equally important. QREasy analytics do not identify everyone who scans, prove that a QR interaction caused a sale, or guarantee leads. They are operational signals for understanding access and code interaction. Treat both totals as behavioral measures, not as verified audience profiles or documented sales outcomes.
A practical next step is to write down the question before reviewing the numbers: Is the goal to know whether the hosted site was reached, or whether a managed code was scanned? Then select the route, note campaign dates and destination changes in your own records, and review the metrics within the available period. For more detail on reading code interactions, see the practical guide to dynamic QR scan analytics.
- Define the event: hosted-site access or managed-code scan.
- Use a static code when the destination URL is fixed and only the content at that URL changes.
- Use a dynamic code when you need scan measurement or a redirect destination that can change without reprinting.
- Keep campaign context outside the analytics so attribution is not overstated.
- Review only within the plan’s available history window.