Enable consent-based GPS location

GPS tracking is optional and applies to eligible managed dynamic scans, not direct static openings. Open your saved dynamic code and review the location-tracking setting before enabling it. Confirm the workspace identity that a visitor will see when asked for permission.

A visitor can share location or continue without it. Browser geolocation needs a secure HTTPS context and permission on the device. If permission is denied, unavailable or times out, the scanning flow should continue without inventing latitude and longitude.

Test the published public link on a real phone. Try both acceptance and refusal, and confirm that each reaches the intended destination. Only the accepted session with a valid device result should produce usable coordinates. A local or insecure URL is not a substitute for production HTTPS.

Explain the reason for location collection in your campaign and avoid treating consent as mandatory when it is optional. If tracking is unavailable, inspect the asset mode, effective plan and service configuration. Ordinary visit counts can still exist without precise GPS data.