Start with two separate measurements
Start by assigning each metric to the action it actually records. A dynamic QR scan occurs when a recipient opens a QREasy-managed redirect. A hosted website visit occurs when someone visits a page created in QREasy. These actions can be connected to one another, but they are not automatically the same event.
Website visits can be recorded no matter whether the visitor arrived through a static URL QR, a dynamic QR, or an ordinary link. A dynamic QR is therefore not required simply to measure visits to a hosted site. Static QR codes do not report scans themselves. The practical guide to dynamic QR scan analytics provides a useful companion for this measurement model.
- Dynamic QR scan: use it to review activity with a managed redirect.
- Website visit: use it to review activity on a hosted page.
- Combined review: compare both over the same period without treating either as a conversion.
- Missing path: acknowledge that a scan does not necessarily lead to a site visit.
Choose the QR type by destination and task
A static URL QR contains one fixed URL. The content at that URL may still change: a hosted page can be updated, or a PDF can be replaced at the same address without reprinting the code. If the encoded URL itself changes, however, a new static QR is needed. A dynamic QR instead uses a managed redirect whose destination can be changed without reprinting, subject to plan limits.
Neither format guarantees that every device will scan it. Nor is a dynamic QR automatically the better choice. If the goal is to edit a QREasy website, a hosted page can do that directly; adding a dynamic code is not necessary merely because the content is editable. When you need a flexible campaign destination, compare the available QR code generators and check the destination behavior before publishing.
Static URL QRs also differ from a QR that contains embedded static vCard data. The former points to a fixed web address; the latter places contact data directly in the code. A digital contact card and a website campaign can therefore require different QR strategies. Record the purpose, encoded destination, and intended next action for every code before looking at its results.
- Fixed URL with replaceable content: a static URL QR can work.
- Destination that must change at the same link: consider a dynamic QR.
- Editable hosted page: use the website; no dynamic QR is required for editing.
- Contact details stored in the code: distinguish embedded static vCard data from a URL QR.
Read the history available in each plan
QREasy’s analytics-history window depends on the plan. This limits how far back you can review scans and hosted website visits. The number of websites, pages, and dynamic QR codes also varies by plan, so compare the plan with the campaign structure before collecting data.
The key is to choose a review period that fits the window available to you. A seven-day Free view is suited to a current check; Lite SME and Business retain 90 days. If a campaign began before the oldest visible date, avoid presenting the visible history as a complete campaign record. Instead, label the period and note that older activity is outside the available history.
- Free: 1 website, up to 1 page each, 1 dynamic QR, unlimited static QRs, and 7 days of analytics history.
- Lite SME: 3 websites, up to 4 pages each, 50 dynamic QRs, unlimited static QRs, and 90 days of history.
- Business: 33 websites, up to 10 pages each, 357 dynamic QRs, unlimited static QRs, and 90 days of history.
- Wallet access: Contact Wallet cards are included on Free; website-linked Wallet cards require Lite SME or Business.
Separate activity from proof of outcome
Analytics do not identify everyone who scans, prove that a scan caused a sale, or guarantee a lead. A recorded scan confirms activity with a dynamic destination, not who the scanner is or what happened afterward. Likewise, a hosted website visit shows that a page was visited, not that a purchase was completed.
Do not subtract scans from visits or calculate a simple conversion rate between them. A scanner may never open the website, while a site visitor may arrive from a normal link. Use each series to describe its own behavior, then add business context such as dated campaign notes or confirmed follow-up records when assessing outcomes.
- Ask what the event means before naming it: redirect activity, page visit, or confirmed business outcome.
- Compare counts only across clearly defined dates and comparable campaigns.
- Keep contact saves and purchases outside the scan count unless a separate confirmed record establishes them.
- Use analytics to guide questions, not to fill gaps in identity or attribution.
Connect Wallet cards, websites, and next actions
QREasy provides digital business cards for Apple Wallet and Google Wallet, along with a small website builder and free QR tools. The supported Wallet journeys let recipients review and save contact details or open a website created with QREasy. Those are useful complements to a QR campaign, but they should still be described as distinct recipient actions.
Contact Wallet cards and the first one-page website are free. Website-linked Wallet cards require Lite SME or Business. For the contact-card side of the workflow, explore the digital business card creator; for the site, begin with website templates. A visit to a linked hosted website can appear in website analytics; a contact save is not itself proof of a sale.
Design each path around one intended next step: review contact details, save the card, visit the website, or take another tracked action in a system that records it. Do not assume that every scan becomes a saved contact or that every saved contact becomes a qualified lead. Clear labeling keeps the business meaning stronger than the raw count.
Run a consistent review in five steps
A consistent review routine reduces the risk of combining unlike measurements. Start with the QR inventory, identify the type and destination of each code, then pull the scan and website histories for the same period. This makes the first question simple: what was measured, over which dates, and under which plan?
After reading the numbers, write a short interpretation. For example: dynamic scans increased during the event window; hosted website visits changed separately; no sales-causation claim is made. If you need background on the service, the information about QREasy can help you map each step to the appropriate tool.
Finally, decide whether the destination, plan, or measurement needs to change. A static URL may be enough if only the page content changes. A dynamic QR is appropriate when the managed destination itself must change. A higher-history plan may help with longer review periods. Make those decisions from the campaign brief and observed behavior, not from an unsupported assumption that one metric explains the whole journey.
- Inventory every active code and mark it as static URL, dynamic, or embedded vCard.
- Confirm each destination and the intended next action.
- Read dynamic scans and website visits separately for the available history window.
- Compare campaigns only when their dates, destinations, and tracking setup are meaningfully alike.
- Document what happened outside analytics without presenting assumptions as tracked outcomes.