In-App Messages appear inside of your app. While standard in-app messages appear as banners, automated in-app messages have various style and layout options. They are stored on the user's device then displayed according to the triggers you define.
See the In-App Message Reference for detail about the options and settings in this tutorial.
Please review your project's Background Push setting status before sending messages via In-App Automation. Background push is used to pre-load in-app messages on a user's device, which increases the speed and reliability of message delivery. It is disabled by default.
You can configure the default appearance of your messages in Settings » Configuration » In-App Automation. Settings include background and heading colors, text colors, size and alignment, etc.
- Open your messaging project from the dashboard, then click Create and select the In-App Automation composer.
- Select a message
style, then click
to move on to the next step.
For Custom HTML, since the message's content and behavior is defined in your provided HTML, the remaining settings and options available in this composer are reduced to only those applicable to the Custom HTML message style.
- Select the message layout, then click to move on to the next step. Layout options vary by message style. Layout is not included if you chose Custom HTML in the Style step.
- Configure the message settings, then click to move on to the next step.
- Select your audience, then click
to move on to the next step.
- All Users: Sends the message to your entire audience.
- Test Users: Predefined recipient groups. After choosing Test Users, select from the Test Groups dropdown menu that appears. See: Test Groups.
- Target Specific Users: Create a recipient group based on available conditions. See: Target Specific Users: In-App Automation.
- Configure the content of your message, then click
to move on to the next step. A preview will
display as you type. Available fields and options vary per message
If you selected Custom HTML in the Style step, the only two sections will be Custom HTML and Custom Keys Additional key-value pairs in your push notification payload for use by custom code in your app. You can use custom keys to pass additional campaign identifiers for analytics, pass user information to the device, control the look and feel of the app, provide image links, etc. . Upload your file now.
- Assign an action for each button, then then click
to move on to the next step. Select from the dropdown menu, then configure its settings.
If you selected Custom HTML in the Style step, the only option in the Actions step is to Set a tag when the message is displayed. See #3 below. You must set other actions within your custom HTML file.
- Button Actions
- (Optional) Set a tag when the button is pressed.
- (Optional) Set a tag when the message is displayed. Use the same search method as setting a tag.
Use this in conjunction with tag-based targeting to prevent a message from being seen or to chain the display of messages. E.g., set a tag “message1” on display of one message, and only display a second message to users who have the “message1” tag.
- Configure the message behavior, then then click to move on to the next step. Select from the dropdown menu, then configure its settings and options. You must configure at least one trigger.
- Review the device preview and message summary, then click Finish.If you would like to make changes, click the EDIT link in the right side of the section header, make your changes, then either click or click the central navigation dot to return to the Review step.
The preview and message summary display only the content and selections configured in this composer; Custom HTML message content must be reviewed independently of the Airship dashboard. We recommend sending yourself a test message.
If you exit before this final step, the message is still a draft and not yet active.