Swrve’s in-app messaging service supports a variety of use cases to help you engage with your customers in a relevant and personalized manner. Use in-app messages to:
- Improve conversion – Send time-limited offers to users who have interacted with the app for a specific period of time, visited the shop at least three times, but not converted.
- Assist users – Provide additional assistance to users stuck on a certain level for a particular time period (and leave those progressing nicely alone).
- Permission opt-in – Increase opt-in rates by requesting device permissions such as push notifications, location, and camera access before triggering the system prompt.
- A/B test message variants – Create up to 10 variations of your message content to test for best conversion (for example, background image, button text or position). For more information, see Localizing and A/B testing campaign content.
- Personalize – Inject user-specific content into your message to ensure relevancy and drive conversion. For more information, see Campaign personalization.
Our new in-app message personalization feature also includes the option to insert dynamic images, text, and call-to-actions.
The in-app messaging service integrates with all of Swrve’s existing analytic capabilities. Before you launch an in-app message (and even after you launch it), QA test alternative messages directly on your device to identify what works and what doesn’t. In addition, use a combination of audience filters and display triggers to specify the precise points at which messages are displayed and limit message frequency and repetition.
In-app messages vs. push notifications
The focus of in-app messaging is communication with users who already have your app open on their device. If you want to communicate with your customers while they’re outside of your app, use Swrve’s push notification service. For more information, see Intro to push notifications.
In-app messaging prerequisites
This section details the technical prerequisites your development team must complete before you can create in-app messages. It also explains how to configure app-level message trigger rules and deeplink URLs for your engagement actions.
Before you can create your first in-app message, your development team must complete the following tasks:
- Configure deeplinks for custom actions – To include custom actions when a user interacts with your message, your development team must configure deeplinks during the integration process. For more information, see the platform-specific integration guides:
- Test in-app messaging in the Swrve service – We recommend your development team test in-app messages on a QA device before you launch your first campaign. The QA test function is available on the QA block of the campaign builder. For more information, see Testing triggered campaigns.
Text styles and custom fonts
Support for custom fonts and text styles is available as of the following Swrve SDK versions: iOS 7.4.0, Android 9.2.0, Unity 8.3.0, and React Native 3.1.0. Any users on older SDK versions of your app will not receive in-app messages that include custom fonts or saved text styles.
Use the In-app message styles screen to upload fonts and create custom text styles. Apply the custom fonts and styles to your in-app message text elements to build completely customized messages that give your customers a recognizable, brand-specific experience.
The Fonts section displays the fonts you have already uploaded. If you delete a font, it is no longer available to use in any new campaigns. All existing campaigns that currently reference the font remain unchanged.
The Text styles section displays the text styles you have already created. The default style applies to all new and draft campaigns. When you create your in-app message campaign, you have the option to apply a saved text style or customize the styling of each text element.
App-level message display rules
Use app-level message display rules to define advanced message display rules before creating your in-app messages. For example, specify a delay before message display, restrict the number of messages displayed per session, or limit the frequency of messages.
To configure message display rules:
- On the Settings menu, select IAM/Conversation display settings.
- On the Messaging Display Rules screen, enter the required values in each statement:
- The maximum number of messages a user can receive in any one session.
- The number of seconds after app start-up that must elapse before the user receives an in-app message. Note: this rule is ignored for any in-app message that you configure to be deliverable when targeted users start an app session (that is, if you select when the user launches the app on the Schedule & display step of the campaign workflow).
- The number of seconds that must elapse between in-app messages.
- To save your app-level display rules, select Save.
- View in-app messaging best practices before you create your message. For more information, see In-app messaging best practices.
- Create an in-app message campaign using our consolidated campaign workflow. For more information, see Creating in-app messages.
- Localize and test variations of your message content. For more information, see Localizing and A/B testing campaign content.
- QA test an existing in-app message. For more information, see Testing triggered campaigns.
- View results and reports for your in-app messages or change the status. For more information, see Managing your campaigns.