What QR code statistics actually measure
Start by identifying the object behind the number. QREasy records dynamic QR scans as one type of event and hosted website visits as another. The history available for each depends on the plan. A website visit can be recorded whether the visitor arrived through a static URL QR, a dynamic QR, or an ordinary link, so website traffic is not automatically a QR campaign total.
A dynamic QR uses a managed redirect. Its destination can later change without reprinting the code, subject to plan limits. In contrast, a static URL QR points to a fixed URL and the code itself does not report scans to QREasy analytics. This makes the distinction between the code and the destination essential when reading any statistics.
Wallet cards are a separate product object, and their availability depends on the plan. QREasy supports digital business cards for Apple Wallet and Google Wallet, including journeys where recipients review and save contact details or open a QREasy-created website. Contact Wallet cards and the first one-page website are free, while website-linked Wallet cards require Lite SME or Business. Learn more through the digital business card creator.
Dynamic QR scans and website visits are separate
Imagine a dynamic QR on a package: it receives a scan, then sends the device toward its current destination. If that destination is a hosted QREasy website, the site can also record a visit. These are two separate measurements. They may occur during one journey, but the analytics should not be used to assume that one scan, one visit, and one person are identical.
Do not calculate a scan-to-visit conversion rate unless the product documentation explicitly defines a reliable way to join the events and states how repeat scans, reloads, and blocked destinations are handled. QREasy's analytics treat the metrics as separate; they do not provide person-level identity or sales attribution.
Use each history for the question it can answer. Dynamic QR history helps compare scan totals for different dynamic codes. Hosted-page history helps review total visit counts for a website, including visits that arrive through static codes, dynamic codes, or ordinary links. For a concrete workflow, see reading dynamic QR scan history and hosted page visits.
Why static QR codes do not report scans
A static URL QR contains a fixed URL. That does not mean the content behind the URL must stay frozen. A hosted webpage can be edited, or a PDF can be replaced, while the URL remains the same; the printed QR continues to lead there without reprinting. Only changing the URL encoded in the code requires a new static QR.
Do not confuse a static URL QR with embedded static vCard data. A URL code sends a device to a web address, while embedded vCard data remains in the code itself. Neither should be described as a dynamic redirect, and the static-code scan limitation should be discussed separately from the vCard format.
If the destination must be replaced later, a static URL code is unsuitable for that job because changing the encoded address requires a new code for previously printed materials. A dynamic managed redirect supports a changeable destination and provides separate scan history, subject to plan limits. Compare formats in the QREasy QR code generators before creating the final code.
Update content and destinations without reprinting
Editing content and changing a destination are different operations. If you replace the page or PDF at the same URL, a static URL QR remains valid. If you need visitors to go to a different URL, you must create a new static code or use a dynamic code whose managed redirect can be updated. A hosted QREasy website does not require a dynamic QR merely because its content will be edited.
Dynamic codes are useful when printed materials cannot be replaced easily, but their scan totals still need careful labels. The managed redirect can change without reprinting, within the limits of the selected plan. Neither static nor dynamic QR codes guarantee that every device will scan successfully, so avoid promising universal readability.
Before deciding, identify what must remain fixed and what must be measurable. A fixed URL plus editable content may need only a static code and hosted website analytics. A destination expected to change, combined with a need for scan history, points toward a dynamic code. The QREasy overview can help confirm which setup fits the workflow.
- Same URL with an updated webpage: keep the static URL QR.
- Same URL with a replaced PDF: keep the static URL QR.
- New destination that is fixed for the campaign: create a new static URL QR.
- Changeable destination with scan history: use a dynamic managed redirect.
- New or edited hosted website: a dynamic QR is not required to record website visits.
Analytics history across QREasy plans
Analytics history is limited by plan, and the retention window differs. Free includes 7 days of analytics history. Lite SME and Business each include 90 days. That means a recent campaign can be reviewed within a short period on Free, while the paid plans provide a longer window for comparing activity across up to 90 days.
The history window tells you how far back you can review a metric; it does not change what the metric means. A dynamic scan remains a scan event, and a website visit remains a site-visit event. In QREasy, the available history changes how far back these separate measurements can be reviewed, not whether they establish individual identity or commercial outcomes.
Website-linked Wallet cards require Lite SME or Business, whereas Contact Wallet cards and the first one-page website are included with Free. When selecting a plan, compare both history duration and the number of dynamic codes, websites, and pages you expect to manage. All three plans include unlimited static QR codes, so static-code quantity is not a differentiator.
- Free: 7 days of analytics history, 1 dynamic QR code, unlimited static QR codes, and 1 website with up to 1 page.
- Lite SME: 90 days of analytics history, 50 dynamic QR codes, unlimited static QR codes, and 3 websites with up to 4 pages each.
- Business: 90 days of analytics history, 357 dynamic QR codes, unlimited static QR codes, and 33 websites with up to 10 pages each.
Interpret statistics without overclaiming
Label every report with the event, source object, date range, and history window. For example, write dynamic QR scans for code A from the last 7 days, not customers from the campaign. Write visits to the hosted website from the last 90 days, not sales attributed to QR traffic. These labels keep the observation aligned with what QREasy actually measures.
Analytics do not identify every person who scans, establish which contact became a lead, or prove that a QR caused a sale. They also do not guarantee lead volume. Avoid claims such as this QR generated revenue or every scan became a customer. A defensible conclusion is narrower: the dynamic code recorded a given number of scans during the selected period, and the website separately recorded a given number of visits.
Make decisions by reviewing trends within one metric, checking whether the destination and campaign timing are appropriate, and recording what changed. If a scan count rises, ask whether more codes were distributed, whether the same code was shared again, or whether the reporting window changed. If site visits rise, consider the mix of static codes, dynamic codes, and ordinary links. Keep conclusions descriptive until another system supplies verified outcome data.
