Deliver relevant, personalized messages to your app’s users with in-app messaging. You can now send messages without relying on users having enabled push notifications. Engaging full-screen, modal, or banner messages are presented while your users are interacting with your app.
To ensure that your app has the latest message data, in-app messages are loaded each time your app comes to the foreground. When your app comes into the foreground, any messages marked for display are prepared to be presented at the top of your app’s view stack. Only one message is displayed each time the app comes into the foreground. Depending on how your app is enabled, the SDK can be triggered to download in-app messages in the background.
You can fully enable in-app messages in Marketing Cloud Journey Builder. To use certain in-app messaging functionality, such as button actions, some SDK configuration is required.
Required Methods for Button Actions
Marketers can configure the action that occurs when an end-user taps a button on an in-app message. Actions for Notification Settings and Location Settings are handled by the SDK, while actions for Web URL and App URL require that you implement URL handling.
You can use the SDK’s optional delegate functionality to control aspects of message display and to get information about the in-app message display lifecycle.
To make your application a delegate of the SDK’s in-app messaging functionality, use
didShowInAppMessage and didCloseInAppMessage
The following delegate methods help ensure that you can appropriately manage your app’s view state. In-app messages are shown as the top view controller in your app’s hierarchy. Your application may need to respond to a view appearing or disappearing.
Prevent or Delay Message Display
You can delay or prevent an in-app message’s display. For example, prevent an in-app message from displaying during loading, instructions, the sign-in flow, and other situations. To prevent display of the message, make the shouldShowInAppMessage method return false.
You can capture the message data and show that message later. For example, present the message after the end-user has signed in. To present the message later, use the following methods.
In-app messages use your device’s system font. You can override the default font face to customize the display of an in-app message title, body, and button labels.
You can’t alter the font size because this is defined by the message’s design.
To set the display font, use the following method to pass the SDK a valid font name for the device’s installed fonts or your app’s custom fonts.
If the font is not a valid font, the SDK returns false and reverts to the system font.
See MarketingCloudSDK+Events.h for more information.