Event Triggers

In the Setup section of the Automation Composer, you must choose which event type will trigger sending your message. Each trigger and its options are detailed here.

Triggers

Predicted to Churn

Predictive Churn tags are available to customers who purchase predictive analytics as an add-on to either an Insight or Connect pricing plan. Consult your Urban Airship Account Manager for details.

Trigger when a user’s behavior results in a change of the predicted likelihood of becoming inactive, or churning. Predictive Churn analyzes your audience for users that exhibit behaviors indicating they are likely to become inactive, and tags the users as High, Medium, and Low risk.

Check to select a risk profile, then use the dropdown menu to apply the trigger when the risk is either added or removed.

  • High risk: Users most likely to become inactive.
  • Medium risk: Users who exhibit signs of potentially becoming inactive.
  • Low risk: Users least likely to become inactive.

See Settings: Configuration: Predictive to enable this for your project.

Tag Change

Trigger when a Tag Change occurs, and select whether it happens when being Added or Removed from a device.


Type ahead to find tags that exist in the system, or create a new tag.

Inactivity

Trigger after a period of Inactivity. Enter your desired number of days.

First Open

Trigger upon the app’s First Open. A delay is required for First Open triggers, with a minimum delay of one hour to ensure delivery. In the Delivery step of this workflow you may specify a number of hours or days after the first time the app was opened.

Location

Trigger based on device Location. Location triggering requires our Gimbal integration.

Select whether this trigger is dependent on when the device Enters or Exits, then click the Select a location button. There are two types of locations available for selection: geofences and beacons. Use the location search dialog to select from the geofences and beacons available to you. Confirm your choices on the Selections tab, then click the Save & Continue button.


See the Location Triggers topic guide for additional detail.

Custom Event

Trigger when an Event occurs, and optionally add a conditional value. See our Custom Events topic guide for more information about custom events.

Type ahead to search custom events that occurred within the last 30 days, then click your selection from the listed results. If there are no results for your searched term, click the Use [search term] button to use the event name as typed.

Add filters to trigger only when the value of an event is equal to, greater than, or less than a specified value. Click the Add value button; choose between equal to, greather than or equal to, or less than or equal to; then enter a value, up to six digits. Click the plus sign to add an additonal filter, maximum two per event.

If you would like to set multiple Event triggers, click the Add another event button and continue with your specifications. Multiple events are handled as a Boolean OR.

Options

Available options appear below the Event Trigger dropdown menu, depending on which trigger is selected.

Rule Limits

Set Rule Limits to define the maximum number of messages this Automation rule will send over a given period of time. The limits set here apply to this automation rule only. Set an automated message delivery limit for this app overall via App-level automation rule limits, an additional Option listed below.

Toggle to enable, then enter the number of messages and days.

Conditions

Define delivery Conditions for this message by specifying one or more tags that must or must not be present on the device. The message will not be sent at all if the conditions here are not met.

Toggle to enable, then choose whether Any or All of the tag conditions must be satisfied before the message is delivered. For each tag, use the dropdown menu to select either Has or Doesn’t have. Has means that the device must have a selected tag in order for the message to be delivered. Doesn’t Have means that the device must not have a selected tag in order for the message to be delivered.

Type ahead to find tags that exist in the system, or create a new tag.

To add further restrictions, click the Add another condition button to add another tag row.

Cancellation Events

Specify Cancellation Events that will prevent a delayed message from being delivered if a selected custom event is received while the message is pending. A minimum delay of one hour is required to ensure there is time for the cancellation event to occur after the triggering event. In the Delivery step of this workflow you may specify a number of hours or days after the triggering event occurred.

Toggle to enable, then complete the same workflow used for Custom Event triggers.

If you would like to set multiple Cancellation Events, click the Add another event button and continue with your specifications. Multiple events are handled as a Boolean OR.

Automation Limits

Edit your Automation rule limits, which control over-notification to users who repeatedly meet automation criteria, capping automated messages per device per given time interval, e.g., a maximum of 4 messages every 10 hours.

Click the pencil icon to make changes. A new window will open to your project’s Configuration settings. Click the Automation Limits tab, and make and save your desired changes. See Settings: Configuration: Automation Limits for detail.