1. Current analytics behavior
For URL-like QR codes routed through QRCraft-managed links, the product currently records aggregate scan counts and compares those counts against plan-based scan limits.
For directly encoded QR types such as WiFi, vCard, email, and SMS payloads, QRCraft does not record dashboard scan analytics because the QR payload is encoded directly and does not route through the QRCraft redirect endpoint.
2. What is not currently provided
The current application does not present a full per-scan event history in the dashboard and does not present precise geolocation, referrer analytics, or device fingerprint reporting as part of the normal analytics experience.
- No dedicated per-scan event table is present in the current application schema.
- No public dashboard currently exposes referrer or device-level analytics.
- Advanced analytics remains roadmap or controlled-rollout functionality rather than a fully shipped analytics workspace.
3. Accuracy notes
Dashboard scan counts should be treated as operational counters rather than audit-grade metrics. Repeated scans, automated traffic, browser prefetch behavior, blocked requests, and network conditions can affect totals.