HOW-TO
Overview
Geofencing allows the FanThreeSixty mobile application to use a fan's location to support event check-ins, location-based communications, and membership point workflows.
Geofencing can be used for several purposes, including:
Allowing fans to check in when they arrive at a venue.
Sending push notifications when fans enter a designated geofenced area.
Automatically checking fans in for an event or awarding membership points, depending on the configured workflow.
A geofence can support many of the same use cases as an audience, with the added condition of a fan's physical location.
Before you begin
Before implementing geofencing, consider the following requirements and limitations:
Location permissions: Fans must have location services enabled and allow the mobile application to access their location.
Geofence radius: The venue's geofence radius can be adjusted to meet the needs of the location and use case.
Push notifications: Communications can be sent when fans enter a geofenced area. Notifications cannot be triggered when fans leave a geofenced area.
Data connectivity: Devices must have a strong data signal for geofencing functionality to work as expected.
Event configuration: Event check-ins require an event with a geofence or location configured.
Configuration support: Work with your Client Success Team to determine the appropriate geofence settings for your use case.
Steps
1. Determine your geofencing use case
Identify what you want to accomplish with geofencing. Common use cases include:
Enabling fans to check in when they arrive at a venue.
Sending push notifications when fans enter a venue or designated area.
Automatically checking fans in for an event.
Supporting membership point workflows associated with an event.
Your intended use case will help determine which configuration options are appropriate.
2. Configure the geofence
Work with your Client Success Team to review the available configuration options and establish the settings for your mobile application.
Three configurable options determine how geofencing and event check-ins behave.
Option 1: Hours Before Start of Event
This setting determines how long before an event's scheduled start time fans are allowed to check in.
Option 2: Auto Check-In
Auto Check-In determines whether fans can be checked in automatically when they enter the geofence associated with an event.
When enabled:
Fans must allow the mobile application to access their location.
When fans check in for the first time, they are prompted to enable Auto Check-In.
Fans can adjust their Auto Check-In preference from the Settings page, accessed through the gear icon.
Automatic check-in occurs when a fan crosses into the geofence associated with an event during the permitted pre-check-in window.
If fans have not enabled location sharing, Auto Check-In will not work as intended.
Option 3: Check-In Requires Geofence
Within the Event Creation form, this setting determines whether a fan must be physically within the event's geofence to check in.
Configuration | Behavior |
|---|---|
On — Required | Fans must satisfy the geofence location requirement to check in. Fans who have chosen never to share their location will not be allowed to check in. |
Off — Not required | Fans can check in without being physically present within the event's geofence. |
3. Validate event check-in behavior
Before using geofencing for a live event, verify that the configuration supports the intended check-in experience.
Confirm that:
The event is configured for fan check-ins.
The event has a geofence or location configured.
The current time falls within the permitted check-in window.
The fan is within the event's geofence when geofence validation is required.
The mobile application has the necessary location permissions.
For automatic check-in, also verify that Auto Check-In is enabled and that the fan has allowed location sharing.
Expected outcome
When geofencing is configured appropriately, the mobile application can use location information to support the intended event and membership workflows.
Depending on the configuration, this can include:
Allowing fans to check in when they arrive at a venue.
Restricting check-ins to fans within the event's geofence.
Automatically checking in eligible fans when they enter the geofence during the permitted check-in window.
Supporting location-based push notifications when fans enter a designated area.
The exact behavior depends on the configured options, event setup, and fan permissions.
Tips and notes
Confirm location permissions: Fans must allow the app to access their location for location-dependent functionality.
Choose an appropriate radius: The geofence radius can be adjusted to suit the venue and use case.
Understand the check-in requirement: When Check-In Requires Geofence is enabled, fans must meet the location requirement. When disabled, fans can check in without being physically present at the event.
Distinguish manual and automatic check-in: Auto Check-In is a configurable feature and requires the appropriate fan permissions and preferences.
Account for connectivity: Devices need a strong data signal for geofencing functionality to work as expected.
Understand notification limitations: Geofence-triggered communications can be sent when fans enter an area, but not when they leave it.
Coordinate configuration: Work with your Client Success Team to confirm the settings appropriate for your use case.
Support escalation
If geofencing or event check-ins are not working as expected:
Confirm that the event exists and has a geofence or location configured.
Verify the event start time and configured pre-check-in window.
Confirm that the fan has allowed the mobile application to access their location.
If using Auto Check-In, verify that the feature is enabled and that the fan has opted in.
If Check-In Requires Geofence is enabled, confirm that the fan is within the configured geofence.
Verify that the device has a strong data signal.
If the issue persists, contact your FanThreeSixty Client Success Team with the event details, configuration settings, and steps taken to reproduce the issue.