What QREasy QR Code Statistics Cover
QREasy’s analytics cover two different events. A website visit is a visit to a hosted QREasy website, whether the visitor arrived from a static URL QR code, a dynamic QR code, or an ordinary link. A dynamic QR scan is a scan of a QR code that uses a managed redirect. These events are recorded separately, so the visit and scan totals should be read as different signals.
Use website visits to assess traffic to a hosted destination and dynamic QR scans to assess use of a particular dynamic code. A hosted website does not need a dynamic QR code for visits to be recorded. The background on what QR code statistics can actually measure is a useful companion when deciding which number answers your question.
- Website visit: traffic reached a QREasy-hosted website.
- Dynamic QR scan: a managed-redirect QR code was scanned.
- Static QR code: no scan count is reported for the code itself.
Static URL QR Codes: Keep the URL, Change the Content
A static URL QR code contains a fixed URL. The printed design can remain in place while the content at that address changes. For example, a fictional bakery can replace an offer PDF at the same URL or update its hosted landing page without reprinting a poster. Only changing the encoded URL requires a new static code.
Use the QREasy QR code generators for this setup when the destination address stays fixed. For a QREasy-hosted destination, website visits are the important measurement. Keep the URL stable, update the hosted content as needed, and compare available website templates before publishing the destination.
A static URL code is different from a QR code with embedded vCard data. QREasy’s digital business card creator supports Wallet journeys for reviewing and saving contact details or opening a QREasy website; website-linked Wallet cards require a paid plan. Embedded contact data is not a managed redirect, so do not expect it to provide dynamic scan analytics.
Dynamic QR Codes: Change the Destination
A dynamic QR code uses a managed redirect rather than permanently embedding the final destination. The destination can change without reprinting, subject to plan limits. This suits a campaign that must move between landing pages while the same poster, package, or card remains in circulation.
Dynamic scans are the relevant code-level measure. A fictional beauty studio can keep one poster code, change its campaign destination, and review dynamic scan history separately from visits to its hosted page. The example in reading a beauty studio’s dynamic QR scan history and hosted page visits illustrates why the two figures should sit side by side rather than be combined.
Neither static nor dynamic codes guarantee that every device will scan them. Test the printed result on several phones under realistic conditions, publish the destination before distribution, and keep it working for the review period. Then examine scan data for dynamic code use and website data for destination traffic.
Measure Website Visits and Dynamic Scans Separately
The distinction affects every result. Suppose a café uses a static QR code on a table: its hosted website can count visits, but the static code produces no scan count. If the café replaces it with a dynamic code, QREasy can count scans of that code and visits to the website, while keeping both measurements separate.
Do not add the totals together. Someone may scan a dynamic code without opening the hosted page, reach the site through an ordinary link, or visit more than once. Website visits can come from static codes, dynamic codes, or ordinary links. The analytics therefore support comparison and trend review, not a person-by-person conversion trail.
- Record the code type and destination URL separately.
- Keep scan and website-visit totals in separate columns.
- Note the print location, start date, campaign changes, and review date.
- Use totals as activity signals, not proof of sales causation.
Analytics History and Plan Limits
Analytics history depends on the plan. QREasy Free includes 7 days of history, while Lite SME and Business each include 90 days. Website visits and dynamic QR scans remain separate measurements within those windows. Choose a review date with the available history in mind: on Free only the last 7 days of data are available, and on Lite SME and Business only the last 90 days, so a campaign that started earlier than that window will show only partial results.
Plan allowances also cover hosted websites, pages per website, and dynamic QR codes. Static QR codes are unlimited on all three plans. Before producing materials, list the number of sites, pages, and dynamic redirects you actually need; this makes it easier to select a plan that fits the intended setup without exceeding its limits.
- Free: 1 website, up to 1 page each, 1 dynamic QR code, unlimited static QR codes, and 7 days of analytics history.
- Lite SME: 3 websites, up to 4 pages each, 50 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history.
- Business: 33 websites, up to 10 pages each, 357 dynamic QR codes, unlimited static QR codes, and 90 days of analytics history.
Choose a Setup and Read the Results Honestly
Choose static when the destination URL will stay stable, content may change at that URL, and website visits are the key measure. Choose dynamic when the same printed code must redirect later and you want a scan count for it. If the destination will not change and scan-level reporting is unnecessary, a hosted website with an ordinary link can still record website visits.
Analytics do not provide unique person recognition, prove that a scan caused a sale, or guarantee leads. A QR code may be one touchpoint in a journey that also includes a search, phone call, or later return visit. Treat the readings as evidence of activity within a known campaign, not a complete account of every person or outcome.
A practical workflow is: define the question, create the hosted destination, choose the code type, test on several devices, record where and when it appears, then review the applicable history window. If the question is traffic to the site, examine visits. If it is use of a dynamic code, examine scans. If both matter, present them together while keeping their meanings clear.
