Visitor Analytics
Track QR code scans, form opens, completion rates, and visitor traffic patterns across all locations.
Last updated on
Visitor Analytics tracks every interaction a visitor has with your QR posters — not just completed submissions, but also scans, form opens, and drop-offs.
Navigate to Analytics in the sidebar to access the visitor analytics view.
Events tracked
Enafeedback records the following events from visitor devices (no cookies or tracking scripts required — data is collected from the server side):
| Event | Description |
|---|---|
scan | QR code scanned (poster URL loaded) |
form_open | The form page rendered |
submission | Visitor submitted a response |
dropout | Visitor left without submitting |
The difference between scan and form_open can reveal QR code readability issues (scan recorded but form never loaded).
Key metrics
| Metric | Description |
|---|---|
| Total scans | Number of QR scans in the period |
| Unique visitors | Estimated unique sessions (de-duplicated by session ID) |
| Form open rate | form_open / scan |
| Completion rate | submission / form_open |
| Drop-off rate | 1 − completion rate |
By location
The location table ranks all active locations by scan volume. A low form open rate at a specific location can indicate:
- QR code is damaged or too small to scan
- Poor lighting at the location
- Wrong poster type for that location
By time
The timeline chart shows scans and submissions by hour of day and day of week. This reveals:
- Peak visitor traffic windows
- Lowest-activity periods (good times for maintenance)
By device
Browser and OS breakdown shows which devices visitors use most. This informs form design decisions (e.g., larger tap targets for touchscreens).
By module
Filter the visitor analytics to see scans and completions for a specific module (surveys, hygiene, feedback) to understand which types of forms perform best.
Privacy
Visitor analytics does not collect:
- IP addresses
- Device identifiers or fingerprints
- Cookies
- Personally identifiable information
Data is aggregated on the server side and stored only as event counts with approximate timestamps. No consent banner is required for visitor analytics collection.