Using Geofencing

There are two steps for using RMC Geofencing:

Step 1: Setup Geofence - Draw a virtual perimeter around a real-world physical location that you would like to target.

Step 2: Create Geofencing Campaign - Target your app users with relevant and engaging push notifications as they enter, exit or dwell within a predefined geofence.


In order for RMC to trigger notifications based on geofence data, your app must receive permission to collect background location from the user and must be configured to work with the RMC platform. For more details, see the RMC Developer's Guide (iOS and Android). Geofencing is available for RMC iOS and Android SDK's latest versions only.




Step 1: Setup Geofence

  1.  Click Target in the top navigation menu, select Geofences from the left panel and click New Definition to create a new Geofence. 

When you are adding a Geofence for the first time, you will see a pop-up as shown below. Click Allow to share your location with the RMC platform.

In the Geofences management panel, you can view and search your previously created Geofences as well as create and import more Geofences.



2.  Enter a Description for the new Geofence, click the Geofence icon located on the map, choose the location you would like to target, drag pointer to determine the Radius and click Save.

















Import Geofences

You can also create Geofences by uploading a list of Geofences that you created outside of the RMC platform. Upload your list of Geofences via a CSV file.



Here's a breakdown of the information needed on the CSV:

FieldDescription
DescriptionThe name of the location

MANDATORY

Latitude and LongitudeThe geographic coordinates for the geofence, formatted as decimal degrees.

MANDATORY

RadiusThe geofence's radius in meters.

MANDATORY

Once you have successfully uploaded your Geofences, you can select New Targeting Action to Create your Geofencing Campaign.

Here the data in the file is kept line by line.




Step 2: Create Geofencing Campaign 

  1. Go to Targeting Actions and click New Targeting Action to create a new Geofencing Campaign.



2.  Enter a Title (name) for your Targeting Action, put a single star (*) in the Pages to be Applied field to prevent page limitations when the action is triggered, choose Geofence as the Type of targeting action.













3.  Fill out the Properties section. Here is a breakdown of the information needed on the Properties section:


FieldDescription
PlatformsChoose the mobile platform (iOS or Android). You can select multiple platforms by clicking ctrl+shift.

MANDATORY

Message TypeSelect the type of message (Image or Text).

MANDATORY

Message TextMessage content for the push notifications. Your messages should be short and to the point.

MANDATORY

Target URLAdd a Target URL to your push notifications to redirect your app users to a given website or landing page.

OPTIONAL

Campaign Tracking ParametersCampaign tracking in RMC lets you track how efficient your marketing campaign is bringing visitors to your website (visits, page views, etc.), how well these visitors convert and how much revenue they generate.

MANDATORY

GeofencesChoose from the previously created Geofences to determine the physical location you would like to target. You can send the same message to multiple locations. Click ctrl+shift to select multiple Geofences.

MANDATORY

Trigger Event

Geofencing notifications are only displayed when an app user triggers a specific geofence. If users don't trigger a particular geofence while the campaign runs, they will not receive the message. The different trigger options are:

  • Trigger on Enter: The notification will be sent immediately when a user goes within the geofence's radius.

  • Trigger on Exit: The notification will be sent immediately when a user leaves the geofence's radius.

  • Dwell: This option allows you to send the notification when a user has been in the geofence for a specified amount of time. For dwelling notifications an amount of time must be specified that a user must remain in the geofence before receiving the notification.

MANDATORY

Send with ExvisitorID?

YES should be selected when sending a request with an ExvisitorID (a specific user ID) for the user entering the geofence field.

  • Send to Last Used Known Token Only?: YES should be selected when the audience to be sent with ExvisitorID wants to be sent only to the last active token values of the user.


OPTIONAL

Open Testing FormEnter exVisitorID (unique user ID) to test your Push Notification.

OPTIONAL

Set Tracking ParameterSet tracking parameter to report analytics on triggered messages.

OPTIONAL

Valid From

Select the start date and time of your new campaign.

MANDATORY

Valid ThroughSelect the end date and time of your new campaign.

MANDATORY

Capping Type

Capping Type is a feature that allows you to limit how many push notifications your app users will get in a given period

  • Visit: Select the maximum number of pushes to users during each visit.
  • Visitor: Select the maximum number of pushes to visitors.
  • Hourly: Select the maximum number of pushes to user on an hourly basis.
  • Daily: Select the maximum number of pushes to user on a daily basis.
  • Weekly: Select the maximum number of pushes to user on a weekly basis.
  • Monthly: Select the maximum number of pushes to user on a monthly basis.

OPTIONAL

Logic operator between rulesYou can choose whether all behavioral conditions (Target Rules) must be met (AND) or at least one of the selected conditions (Rules) must be met (OR).

OPTIONAL

Target RulesSend Push Notifications based on multiple targeting rules like subscribers enrollment time, user segment, behaviour or define any rule of your choice with rule-based targeting.

OPTIONAL


4. Click Save to record the changes.

Mission Complete! You now have created a Geofencing Notification for your app users entering/exiting the selected Geofence(s).



Examples and Use Cases

Best practices for using RMC Geofencing:



Additional Information

Please check the following pages for additional information:



Parent Topic: Geofencing

Copyright 2020 Related Digital