In the Setup step of the Automation Workflow, you must choose which event type will trigger sending your message. Each trigger is detailed here, along with Options and Project Settings.
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, or 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.
Trigger when a tag is added or removed from a device.
Type ahead to find tags that exist in the system, or create a new tag, then use the dropdown menu to apply the trigger when the tag is either added or removed.
Trigger after a period of inactivity. Enter your desired number of days.
The initial inactivity period starts at the time the trigger is created, so the number of days entered must elapse before the message will be sent.
Trigger based on when the app is opened for the very first time. The behavior of the First Open trigger varies by platform:
- For mobile apps, trigger upon the app’s First Open.
- For web browsers, trigger upon the user opting in to web notifications.
A delay is required for First Open triggers, with a minimum delay of one hour to ensure delivery. In the Delivery step of the Automation workflow, you may specify a number of hours or days after the first time the app was opened or the user or opted in to web notifications.
Trigger based on device location.
Trigger based on location attributes. Attributes are key/value pair metadata associated with a particular location.
Trigger when an event occurs, and optionally add a conditional value or property. See: 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.
If you would like to set multiple Event triggers, click the Add another button and continue with your specifications. Multiple events are handled as a Boolean OR.
Named user event automation does not support tag operations. An automation pipeline with tag-based operations and custom event triggers attributed to named users will not run.
Optionally trigger only when a specified property or value is met. Filter by a numeric value associated with the event, or by key/value properties attached to the event.
- You may have a custom event named “Purchase,” with a numeric value
representing the dollar amount of the purchase
125.0, as well as key/value pairs for a product SKU
1359DUKSand a purchase category
fedoras, potentially targeting users spending more than $100 on fedoras.
Acceptable values and operators for properties are based on configuration settings. See: Settings: Configuration: Event Properties.
- Click the ADD PROPERTIES/VALUES button.
- Click the Add Property or Add Event Value button.If you would like to set multiple filters, click the Add Property or Add Event Value button again and continue with your specifications. Click the X at the end of any additional row to remove it.
- Choose from the dropdown menu and complete the filter. For Properties, click
Search for Properties, enter a search term, and click to select from the
These operators are available for both Properties and Values. Enter a numeric value.
Greater thanThese operators are available for Properties only. Acceptable values vary.
Greater than or equal to
Less than or equal to
Equals: Enter an alphanumeric value.
Is (true/false): Select true or false.
Contains: Enter an alphanumeric value.
- Optionally add an alternative by clicking the plus sign icon at the
end of a row.
- 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)
If set to ALL, filters with alternatives use a Boolean OR operator. If set to ANY, filters with alternatives use a Boolean AND operator.
- Click the Save button, or Cancel to discard.
Available Options appear below the Event Trigger dropdown menu, depending on which trigger is selected.
Specify 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 project-level automated message delivery via Automation Limits, listed below.
Toggle to enable, click Add a Daily Limit and/or Add an All-Time Limit, then enter a number of messages for the selected period. For the daily limit, also specify the number of days.
Specify one or more tags that must or must not be present on the device for the message to be delivered. The message will not be sent at all if the conditions here are not met.
Named user event automation does not support tag operations. You cannot set tag conditions if your event trigger is a custom event attributed to named users.
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.
Specify the 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.
Project Settings are at the bottom of the screen, following the Options.
Automation Limits 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.