A Geofence is a virtual boundary around a particular location. You can define Geofences in the system and then use them to trigger Events. For example, a customer entering (or nearing) a store could trigger the Geofence for that store. This could in turn trigger an Event whereby the customer is presented with an appropriate action. You can also reference Geofences in strategies and can harness this to determine the most relevant action for a particular customer.

Geofences are accessible in the Pega Customer Decision Hub portal, via: ContentReal-Time ArtifactsGeofences.

The Geofences landing page provides a quick overview of the various fences configured in the application. The Geofence rule can be opened by double-clicking the Geofence row.

• Understanding geofences

  The rendered map is a Google map and allows for various interaction patterns, including the following:

• Creating a geofence

  Users can use the Create link in the Geofences landing page to create a new Geofence.

• Importing geofences

  Use the Choose File button to select the comma-separated values (CSV) file containing the list of Geofences to import. After selecting the CSV file, use the “Next” button to proceed to the review stage.

• Associating a real-time event with geofences

  Events that have been associated to this Geofence are displayed in the “Associated Events” grid. When a customer enters this Geofence, the Events listed in the grid will be triggered. Refer to the Events chapter for details on associating Geofences with Events.

• Understanding geofence services

  In addition to configuring Geofence rules in Pega Customer Decision Hub , the app that wishes to detect when a Geofence is entered (tripped) must make service requests to the system to determine if a Geofence is tripped. If a Geofence is tripped, all Events associated with it will be triggered (assuming they are currently applicable). The system provides multiple services which can be used separately or in tandem to facilitate this functionality.

• Understanding the Preferred Geofences services

  The Preferred Geofences set of services can be used to determine the most relevant set of Geofences for a particular location. For example, when a customer launches the app on their device, the app can invoke the service to determine the list of nearby Geofences to monitor. The app can then provide this list to the device’s OS to monitor, thereby avoiding having to continually poll whether the current location has tripped a Geofence.

• Understanding the Detect/Trigger services

  The Detect/Trigger set of services are used to detect whether a customer’s device has tripped a Geofence in the system and to trigger Events associated with tripped Geofences. These services support handling requests for multiple customers in a single request.