Location Triggers Tutorial

Use location data to trigger real-time Automated messages. This page details the configuation of location triggers.

Event triggers are events that cause an automation to send messages to individual members of your audience. You set a single event trigger during the Setup step of the Automation composer. In this tutorial you will configure the three location-based event triggers.

 Important

Location triggers require integration with our location data partners. Configure the integrations before using the triggers.

  • The Location and Location Attibutes triggers require Gimbal integration.
  • The Events trigger requires Radar integration.

Configure the Location Trigger

  1. Open your project from the dashboard, then click Create and select the Automation composer.
  2. Enter a descriptive Automation Name, then select the Location trigger.
  3. Click Select a Location.
  4. Enter a search term in the box. Results, if any, display on the map and are listed in the Results tab.There are two types of locations available for selection: geofences and beacons. Click on a result for a detailed view of a location. If selecting a geofence, the map to the right will zoom to the selected location. Click and drag, and use the +/- zoom controls to change the displayed area.
  5. Check the box next to the locations you want to use as the message trigger.
  6. Review the locations on the Selections tab, click the X next to any location you'd like to remove, then click Save & Continue.Your selected location(s) will be listed in the trigger selection pane. Click the X to remove a selection.
     Note

    You can select a maximum of 20 locations per automated message.

  7. Use the dropdown menu to choose whether to trigger when the user enters or exits a selected location.

Now you are ready to complete the remaining steps in the Automation composer.

Configure the Location Attributes Trigger

  1. Open your project from the dashboard, then click Create and select the Automation composer.
  2. Enter a descriptive Automation Name, then select the Location Attributes trigger.
  3. Enter a key/value pair for the location you want to use as the message trigger.If you would like to set multiple attributes, click Add Another and continue with your specifications. Click the X at the end of any additional row to remove it.
     Note

    You can add a maximum of 50 attributes per automated message.

  4. Optionally add an alternative key/value pair by clicking the plus sign icon at the end of a row.
  5. Use the ALL/ANY dropdown menu to choose what criteria must be met.
    • ALL = all criteria must be met (Boolean AND)
    • ANY = any criteria must be met (Boolean OR)
       Note

      If set to ALL, attributes with alternatives use a Boolean OR operator. If set to ANY, attributes with alternatives use a Boolean AND operator.

       Note

      By default, the notification will be triggered if the location attributes meet ALL the attributes you entered. For example, if you selected ALL, with attributes half_off and has_cafe, you’d only reach users who entered or exited a location that met both of those conditions. If you selected ANY, you’d reach all users who entered a location running a half-off campaign as well as all users who entered a location that has a cafe.

  6. Use the dropdown menu to choose whether to trigger when the user enters or exits a location.

Now you are ready to complete the remaining steps in the Automation composer.

Configure the Event Trigger

 Tip

These steps are a version of the Custom Event trigger documentation, with the options and settings relevant to the Radar integration.

  1. Open your project from the dashboard, then click Create and select the Automation composer.
  2. Enter a descriptive Automation Name, then select the Event trigger.
  3. 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.
  4. (Optional) Click Add Another to add more Radar event triggers. Multiple event triggers are handled as a Boolean OR.

Now you are ready to complete the remaining steps in the Automation composer.

Filter

When setting Custom Event triggers, you can filter your 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 automated message when a user enters a Radar geofence (radar_geofence_entered) with a confidence property (radar_confidence) value of Medium.

After configuring the Event trigger in the Setup step of the Automation composer:

  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. This determines not only multiple filters, but also alternatives within each filter.
    • ALL = all criteria must be met (Boolean AND)
    • ANY = any criteria must be met (Boolean OR)
       Note

      If set to ALL, filters with alternatives use a Boolean OR operator. If set to ANY, filters with alternatives use a Boolean AND operator.

  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