Scan location looks wrong
Scan locations are approximate and should be used for trends, not exact visitor identity. A scan may appear in a nearby city, carrier hub, or VPN location.
Why locations can be approximate
QRSurge location analytics use available network and request signals. Those signals are useful for broad campaign reporting, but they are not the same as GPS tracking.
Location can look different from the scanner's physical position because of:
- Mobile carrier routing.
- VPNs or privacy tools.
- Corporate networks.
- Public WiFi providers.
- Browser and device privacy settings.
- IP databases that map to a nearby city or region.
Use location data for trends
Map view and location analytics are best for understanding patterns across many scans. Use them to compare regional trends, top locations, and map clusters where available.
Avoid using scan location as proof of one person's exact position. It is better for questions like which markets responded, which cities scanned most, or whether an offline campaign reached the expected region.
Check the date range and QR code scope
If a location looks unexpected, check the selected date range and whether you are viewing organization-wide analytics or analytics for one QR code.
Organization-wide views can include scans from multiple campaigns. Individual QR code analytics are better when you need to review one placement or campaign.