Tutorial: How to configure the participation requirement by Location Follow
Location-based participation allows you to restrict access to a promotion to users who are physically located in one or more locations defined by the organizer.
To do this, the system requests permission to access the participant's device location and verifies that it is within the area configured for one of the participating locations. Only when the validation is successful can the user access the promotion.
This requirement is ideal for campaigns where participants must visit a store, restaurant, event, office, or any other physical establishment to participate. In this tutorial, you will learn how to configure location-based participation and how to view information and statistics about the locations from which users participate.
1. What is the user experience and how is their location validated?
2. How to create the requirement based on the users' location
3. How to manage location information and users participations
4. Locations statistics
1. What is the user experience and how is their location validated?
The location requirement is presented immediately before the user participates in the dynamic you created, whether they are simply checking in to discover if they have won a prize, playing a game, answering quiz questions, trying their luck with a scratch card or prize wheel, and so on.
Depending on the participation flow, the location requirement may appear either immediately after registration (in Identified mode) or before the entry form (in Visitor mode), where participation takes place before user registration. Discover here more about the participation flows available.
Users will be prompted to enable location services on their device and grant permission to access their location. They can choose to allow the page to access their location every time or only on that specific occasion.
In the following video, you can see an example of the user experience for a prize wheel available exclusively to users who visit the brand's stores:
2. How to create the requirement based on the users' location
The first step to create the requirement to validate the user's geolocation to grant access to the participation stage will be to create the valid locations, from which users will access and participate. To do so, enter the Editor > Prizes > Locations:
See here the step by step tutorial to create and customize the Locations.
Once you have created the locations, you can configure the user geolocation requirement, from the Participation Stages section > Requirements tab, where you can create a location-based participation requirement. There, you will find the following options:
- Select Location as the requirement type.
- Requirement frequency: Choose whether the user must be physically located at one of the selected locations every time they participate or only on their first participation.
- Location validation: Select one or more valid geolocations from which users will be allowed to participate.
Once you have selected the locations from which users will be allowed to participate, you can configure and customize the following options:
- Unit system: Select the measurement system used to calculate the user's distance and geolocation: Metric or Imperial.
- Validation radius: Set the maximum allowed distance between the physical location and the user's device location (from 25 to 500 m). This allows you to adjust the validation accuracy based on the size and characteristics of each location.
- Display the location description, address, and/or logo: Enable these options if you want to provide users with additional information about the participating locations, in case they tried and participate from a location that is not valid. The information displayed is taken from the settings configured in the Locations section of the editor.
- Limit participation by location: Restrict how often the same user can participate based on their physical location. For example, you can grant one prize wheel spin for each new store the user visits. This way, the user can participate only once from each store.
- Customize the location requirement page: Personalize the participation requirement page by adding a header image, an informational message displayed before requesting access to the user's location, and a button that allows users to grant permission and continue with their participation.
3. How to manage location information and users participations
As the promotion administration, you can access and see or download all the users data, including the location information, to see where users participated from.
The information is available under the User Manager, where you will be able to see the details of each user's participation.
Enter here to discover more about the User manager and its features.
3.1. How to view location information to see where users participated from?
By accessing the information of a specific user, the location will also be reflected in each of their participations. To access the details of the user's participations, click the "eye" icon:
3.2. How to filter location information to see where users participated from?
The User Manager allows you to filter the list of participants based on the location from which they participated. To do this, apply the Stages > Location filter and then select the location or locations you want to filter by.
3.3 How to download the location information
You can download user information and their entries, generating a file that will include the location from which the user accessed to participate, by going to Export > Participations, as shown below:
4. Location statistics
From the promotion’s Statistics section, you will be able to see the total number of times users have accessed the location requirement page, in order to evaluate traffic, as well as view a chart with the total participations by location.
In promotions with the location-based participation requirement enabled, employees will be able to view statistics for all participations generated at their location from the Seller Portal.
Comments
0 comments
Article is closed for comments.