If you're planning to use both Custom Domain feature and GPS Tracking feature, then this guide is highly relevant to you. 

When you setup a custom domain/sub-domain (say http://qr.mywebsite.com) and point the domain to scnv.io via CNAME record, you're able to mask Scanova's URL (of the format https://scnv.io/AbCd?qr=1) of redirection/landing page with your own URL (say http://qr.mywebsite.com/AbCd?qr=1). This URL is now encoded into the QR Code, instead of Scanova's URL. 

Now when a user scans the QR Code, the URL (of your domain) runs in the mobile browser of the smartphone used to scan the QR Code. 

Now say, you have enabled using the GPS tracking feature. This means that ideally, when the user scans the QR Code, they should see a permission dialog:

This means that the browser is allowing the site to take location permission from the user. 

Due to security enhancements, mobile browsers (such as Chrome) are now allowing only SSL-certified URLs (URLs with https) to take permissions. This means that if Chrome encounters an http domain (say your domain that is not SSL enabled) then it will skip the permission step and directly display page content or redirection. 

This means GPS tracking feature will not work for all mobile browsers if SSL is not enabled on the domain/sub-domain setup via the Custom Domain feature. 

We're currently conducting browser-level tests and we'll update this guide with details on behaviour of specific browsers. 

If you have any further questions or concerns, please reach out to the support team at [email protected]

Did this answer your question?