In-app automation is initiated by a trigger, such as a opening your app, viewing a particular screen in your app, or elapsed time. There are many uses for in-app automation:
- Dsiplaying a "Welcome" message when users first open your app.
- Displaying a "Tip" message when a new feature is added to your app.
- Asking a user to rate your app after they have opened it for the 6th time.
While standard in-app messages appear as banners, in-app automation messages have various style and layout options. See the In-App Message Reference to learn more about the differences.
In-app automation is designed to be highly contextual and displayed immediately in response to user behaviors, e.g., the user opens the app a specific number of times, views a specific screen, adds an item to the cart, makes a purchase, or views a video. Respond to user behaviors instantly with customizable messages, giving you precise control of the user experience.
- Real-time Display
- In-app automation uses our on-device automation framework, which means they can respond to a series of events in real-time (e.g., multiple game level changes, a sequence of screens, additions to a shopping cart) without round-trips to a server.
- Guaranteed Delivery
- In-App Automation is designed to use background push to reliably deliver in-app messages by sending a broadcast background push to all of your app users.
When background push is enabled for your project, we pre-load in-app messages in your app via a background push. When background push is disabled for your project, or for users opted out of background app refresh, our SDK downloads and refreshes the entire message list upon next app open.
Background push is disabled by default, though we strongly encourage enabling it if your app can handle it.
- Control all aspects of the message, including branding, through our dashboard.
- Localization Support
In-App Automation supports localization for all message styles. Instead of creating individual messages for different locales The combination of a language and country. A user's locale is determined by their device settings. , you can create a single message and provide variations for each language you want to reach your audience in. Airship sends the appropriate localization to each member of your audience based on device settings gathered by the Airship SDK.
When you compose a message that you want to localize, you will upload a CSV containing your language variants. When Airship receives your upload, it automatically creates a localized message for each language or locale. You can then preview and edit each localized message in the In-App Automation composer.
For your convenience, Airship provides a sample CSV for download in the Content step when creating your message. When you upload custom HTML, the sample CSV file contains columns for
data-ua-id-associated elements in your custom HTML.
You can set up in-app automation in the dashboard.
- Dashboard: In-App Automation composer
- API: Not supported
See also: Display Triggers.