Read the labels before comparing totals
The channel describes how an event reached QRTech’s tracking route. A QR-labelled address can be copied and shared as text, so a QR event does not prove that a camera scanned a particular poster. Similarly, a normal link may travel through several messaging apps before someone opens it.
- Keep labels consistent when distributing your page.
- Missing source information does not reveal the placement.
- Compare the same resource and date range before drawing conclusions.
| Label | What it represents | What it does not establish |
|---|---|---|
| QR | A visit through the QR-labelled route | A verified scan of one physical sign |
| Link | A normal link visit, including no source marker | Which message or profile caused it |
| Outbound | A recorded link-list destination action | A completed booking, purchase or review |
| Unknown | A visit with an unrecognized source marker | A known physical or digital placement |
Count actions without turning them into people
One visitor may open a page more than once and follow several destinations. The totals therefore cannot be read as a unique audience or added together to calculate the number of people reached. Your own testing can also influence a small set of results.
For example, 120 recorded page visits and 30 outbound actions are useful counts, but “25% of visitors converted” assumes a relationship those totals do not establish. There may be repeat visits, several actions by one person or actions unrelated to the outcome you care about. Describe the counts plainly before assigning a business meaning.
Separate interest from a completed result
An outbound action records a tracked link-list destination route. Other native page actions are not all counted as outbound. The external service decides what happens next: a click toward Google reviews is not a published review, and a click toward booking details is not a confirmed reservation. Check the final outcome in the service handling that task.
QRTech form responses are a separate source of evidence about submitted information. Review the actual responses and the fields people complete, rather than interpreting page visits as submissions. Forms require Premium. Choose fields that help you answer the enquiry, and avoid collecting details you have no practical use for.
Leave room for activity that is not recorded
Recorded totals are not a complete census. Analytics can be disabled, privacy preference signals can suppress collection, and some requests are excluded. Available history also depends on retention and service configuration. Country, device and browser groupings describe recorded traffic broadly, rather than identifying an individual visitor.
Native Wi-Fi scans do not travel through QRTech’s redirect route because the credentials are encoded in the symbol. They cannot be interpreted as measured redirect visits. A lack of QR events for a Wi-Fi sign does not tell you whether guests used the network successfully.
Make one change you can explain
Choose a question before opening the chart: do people notice the enquiry action, or is a practical answer too far down the page? Compare similar periods, note holidays or campaigns, then change one meaningful element. Moving an action and rewriting every section at once makes the result difficult to interpret.
- Write down the page’s intended action.
- Record the date range and counts you are comparing.
- Inspect the page on a phone for likely sources of friction.
- Make one content or placement change and note its date.
- Review a comparable period and check actual outcomes separately.
Questions, answered.
Are visits the same as unique visitors?
No. A person can generate several recorded events. Use the reported labels as activity counts and avoid claiming a unique audience from them.
Can I identify which table a scan came from?
The QR channel alone does not identify a table or poster. You need a deliberate distribution setup and should verify what the available resource-level reports actually distinguish.
