Urban Airship launches in app automation engine
|Richard Harris in Messaging Friday, March 16, 2018|
In-app automation engine for sending off in-app messages and prompts has been announced by Urban Airship.
Marketers and mobile app product owners can now use Urban Airship’s UI to fully customize native templates or custom HTML for different rich, interactive message layouts, define automation logic, edit messages and view their performance. This skips the uphill battle of getting developer resources during app update cycles for instant in-app messages, saving marketers time and expense, and offering new levels of flexibility to address key onboarding and engagement opportunities.
The in-app automation engine includes out-of-the-box actions for common onboarding and engagement use cases, including: welcome messages, opting in to notifications, registering, rating apps, feature adoption and wallet pass installation. Fine-grained controls and adaptive messaging triggers offer new levels of customer-centricity, as well as the ability to define start and end dates, suppress or repeat messaging they’ve seen before, configure message priority, target messages to specific screens and manage opt-outs for GDPR compliance.
“The vast majority of customer journeys today are self-directed, and digital offers consumers effortless, limitless choice, so it’s more important than ever to engage people as they learn about brand offerings and features - it’s their point of maximum influence,” said Brett Caine, president and CEO, Urban Airship. “We’re on a mission to disrupt the status quo of digital customer engagement, making it easier and more automatic to use customer data and drive action across all digital channels.”
Previously, automation logic for every in-app messaging solution lived only in the cloud, requiring server roundtrips for segmentation changes and delivery. As users take actions within apps and fall in and out of different segments, new messages become more appropriate than old ones, and roundtrip delays result in missed messages or messages appearing screens later after the user’s context has changed again. Marketers’ only other option was getting developers to define fixed triggers to instantly display messages, resulting in inflexible messaging at an unsustainable resource cost.
Now, instead of triggering a message on “item added to cart” or “product purchased,” marketers can use other event metadata (SKU, product category, order value) and user attributes (loyalty level, language and/or country code) for more personalized and localized messaging. App product owners can get more sophisticated about feature adoption, for example promoting the app’s community reviews section when three or more products in a category are viewed and they have not yet used this feature. This message could be shown only once or repeated, or it could trigger additional messages based on recipients’ message button taps. Those tapping “not now” could be added to an automation that instantly displays a message on a target product screen every fifth app session with at least one week between messages and ending on their 20th session.
These behavioral events and message response data are also available for triggering server-side automations or cross-channel segmentation, as well as deeper ad-hoc analysis or real-time streaming to any other business system or data warehouse. For example, if users still haven’t installed their mobile wallet coupon for registering with your app, send them an email on Day 3 and repeat, suppress or prioritize its delivery to any other digital channel.
Write and run code every step of the way, using Android Studio to create apps that integrate with other apps, download and display pictures from the web, play sounds, and more. Each chapter and app has been designed and tested to provide the knowledge and experience you need to get started in Android development.
How to create a profitable, sustainable business developing and marketing mobile apps.