Geofencing in Onboarding: Setup and How It Works

What is geofencing and how does it work?

Geofencing restricts onboarding based on a user’s physical location. It’s commonly used for regulatory compliance or phased rollouts to ensure onboarding is only available in approved countries.

When enabled, the SDK requests location permission at the start of onboarding. Once permission is granted, it captures the user’s GPS coordinates, converts them into a country code, and checks this against your list of allowed countries. Users located in approved countries can continue onboarding. Users in blocked countries see a message indicating that onboarding is not available in their current location.

If a user does not grant location permission, they will see an error message explaining that location access is required to proceed. We currently store the logs (lat, lng, country, etc) of the user for 30 days in our database.

2. How do I enable geofencing?
To enable geofencing, navigate to the Onboarding Configuration page within the Template Settings of the relevant template.

By default, onboarding is allowed from all countries. In the Onboarding Locations section, deselect the countries where you want to block onboarding and click Update. Once saved, users from the deselected countries will no longer be able to complete onboarding.