You can trigger automation and journeys based on location events, e.g., a user’s movement in and/or out of a geofence or proximity to a beacon signal. You configure triggers in the Setup step in an automation or Trigger step in a journey. In this tutorial you will configure the three location-based triggers. See also:

• Location Triggers feature guide
• Automation tutorial
• Journey tutorial

Location

The Location trigger initiates an automation or journey based on an audience member’s device location. You can select a maximum of 20 locations per automation or journey.

In the Setup step in an automation or Trigger step in a journey:

1. Select the Location trigger.

2. Click Select a Location.

3. Enter a search term. Results, if any, display on the map and are listed on the Results tab.

   There are two types of locations available for selection: geofences and beacons. Click a result for a detailed view of a location.

   

   If selecting a geofence, the map will zoom to the selected location. Click and drag, and use the **+/-** zoom controls to change the displayed area.

   

4. On the Results tab, check the box next to the locations you want to use as the trigger.

5. Review the Selections tab, then click Save and continue.

6. (Optional) Click Select a Location to add more locations.

7. Choose whether to trigger your automation or journey when the user enters or exits a location.

Location Attributes

The Location Attributes trigger initiates an automation or journey based on key/value pair metadata associated with a particular location.

You can add a maximum of 50 location attributes per automation or journey.

In the Setup step in an automation or Trigger step in a journey:

1. Select the Location Attributes trigger.

2. Enter a key/value pair for the location you want to use as the message trigger.

   

3. (Optional) Click   to add an alternative location attribute.

4. (Optional) Click Add Another to add more location attributes.

5. Select ALL/ANY to determine how to evaluate multiple location attributes and alternatives within each location attribute.

   • ALL = all criteria must be met (boolean AND)
   • ANY = any criteria must be met (boolean OR)
    Note

   By default, the automation or journey is triggered if the audience meets ALL the location attributes. For example, if you selected ALL, with attributes half_off and has_cafe, you’d only reach users who enter or exit locations that meet both conditions. If you select ANY, you’d reach all users who enter a location running a half-off campaign as well as all users who enter a location that has a cafe.

6. Choose whether to trigger your automation or journey when the user enters or exits a location.

Event (Custom Event)

In the Setup step in an automation or Trigger step in a journey:

1. Select the Custom Event trigger.

2. Use the Events box to find a Radar event, then click to select from the listed results. The search shows events that occurred in the last 30 days. All Radar events have the prefix radar in the name, e.g., radar_geofence_entered.

   

3. (Optional) Click Add Another to add more Radar events. Multiple event are handled as a boolean OR.

   

Filtering Custom Events

When configuring the Custom Event trigger, you can filter custom events using numeric values associated with those custom events, or by key/value properties attached to the events. Filtering events this way can help you more precisely target your audience.

Each Radar location event has associated properties that may be used as filters. For example, you can choose to trigger an automation or journey when a user enters a Radar geofence (radar_geofence_entered) with a confidence property (radar_confidence) value of Medium.

1. Click ADD PROPERTIES/VALUES for the custom event.

   

2. Click Add Property.

   

3. Click Search for Properties, enter a search term, and select from the listed results.

   

   

4. Set the property or value for your event filter and the operator determining how you want to evaluate the property or value. An operator will pre-populate for most properties. Equals is used for radar_confidence only.

5. (Optional) Add an alternative by clicking the plus sign icon at the end of a row.

6. Select ALL/ANY to determine how to evaluate multiple filters and alternatives within each filter.

   • ALL = all criteria must be met (boolean AND)
   • ANY = any criteria must be met (boolean OR)

7. Click Save.

Radar Events and Properties

Use the following terms when searching for and filtering Radar events. See Radar’s documentation for additional detail.

Each event is followed by its associated properties and each property’s acceptable value.

Radar Geofences

radar_geofence_entered

radar_geofence_description: String
radar_geofence_tag: String
radar_geofence_external_id: String
radar_confidence: Low, Medium, or High

radar_geofence_exited

radar_geofence_description: String
radar_geofence_tag: String
radar_geofence_external_id: String
radar_confidence: Low, Medium, or High
radar_duration: A number, in minutes

Radar Insights

radar_home_entered

radar_confidence: Low, Medium, or High

radar_home_exited

radar_confidence: Low, Medium, or High

radar_office_entered

radar_confidence: Low, Medium, or High

radar_office_exited

radar_confidence: Low, Medium, or High

radar_traveling_started

radar_confidence: Low, Medium, or High

radar_traveling_stopped

radar_confidence: Low, Medium, or High

Radar Places

radar_place_entered

radar_place_name: String
radar_place_chain_slug: String
radar_place_chain_name: String
radar_place_categories: String
radar_place_facebook_id: String
radar_confidence: Low, Medium, or High

radar_place_exited

radar_place_name: String
radar_place_chain_slug: String
radar_place_chain_name: String
radar_place_categories: String
radar_place_facebook_id: String
radar_confidence: Low, Medium, or High
radar_duration number: A number, in minutes