In-App messaging is a messaging channel that allows you to display a message when the user is active within the mobile application. This message type is complimentary to push notifications which are delivered to the notification center of users’ phone. For more information on the push notification channel, refer to this section.
This channel requires mobile applications to be integrated with Adobe Experience Platform SDK. These apps have to be activated in Adobe Experience Platform Launch before being available in Adobe Campaign for In-App deliveries.
To start sending In-App messages on mobile applications leveraging Experience Platform SDK, you need to meet following prerequisites:
In Adobe Campaign, make sure you can access the In-App channel. If you cannot access these channels, contact your account team.
To leverage mobile use cases in Adobe Campaign Standard with an Experience Cloud SDK application, a mobile app has to be created in Adobe Experience Platform Launch and be configured in Adobe Campaign Standard. For the step-by-step guide, refer to this page.
Once configured, you can now prepare your In-App message. For more on this, refer to this page.
Your delivery is now ready to be sent. To learn more, refer to this page.
Check out the resources below:
Since In-App messages are pulled by the SDK from Campaign, we want to provide a secure mechanism to ensure that In-App Messages containing PII data do not fall into malicious hands. As such, we have following mechanism in place to ensure the secure delivery of messages to the device:
You need to configure In-App tracking postback. Instructions can be found here.
To implement local notification tracking, refer to this page.
An out-of-the-box report is available in Adobe Campaign for In-App channel. Refer to this documentation.
See this page to understand how each In-App metrics are calculated.
There are no multi-lingual templates available for In-App Messaging now.
However, if the objective is to send an In-App message in a language other than English, the content can be directly pasted in the available text boxes.
No, this is not yet supported.
For alert messages, at least one dismiss button (primary or secondary should have action dismiss) is required. Otherwise, it is possible to save the message but it will not be received.
For custom sound on iOS, you need to provide a file name with extension when creating a local notification (for example, sound.caf). If this extension is not provided, then the default sound is used.
Yes, deeplinks are supported in In-App messages. Deeplinks should include:
Yes, these messages are also referred as daisy chain messages. Follow the process below:
Create an In-App Message.
Define a custom event and select it as an event trigger for this IAM e.g. “Trigger from fall preview Push”.
When authoring your Push message, define a custom variable whose value can be set as an event used to trigger IAM e.g. Key = “inappkey” and value = “Trigger from fall preview Push”.
In the mobile app code, implement event trigger as follows: