This information helps you troubleshoot in-app messaging.
If you have completed all the requirements for In-App Messaging, but messages do not display, check the following items:
Ensure that you have an In-App Messaging section in your configuration (downloaded JSON file) or have a Messages remote endpoint, so that it can be retrieved from dynamic tag management.
Did you update your manifest file to define the full screen activity?
Ensure that the local notification broadcast receiver is declared in your manifest. For more information, see step 2 in Enabling In-App Messaging in In-App Messaging.
To verify whether your message is live, on the Manage In-App Message page, in the Status column, check the list of messages.
Verify that these settings are set the way you want. On the Audience tab, review your Trigger options, which allow you to specify how often the message is shown.
Launch only fires on a new session. For more information about when a session begins, see the
lifecycleTimeout row in JSON Config.
Remember the following information:
For more information, see Lifecycle Metrics.
The In-App Message full-screen template supports displaying an image from a remote server (Image URL) or from the app bundle (Bundled Image). The image should be in a standard image format, such as JPG, GIF or PNG. Because device screens have many different dimensions, the image will most likely not fit exactly into the space provided by the template. The template focuses on showing the center of the image and, if the image does not fit, crops (portrait) or fades (landscape)the sides.
Here is the exact placement and sizing rules for each orientation:
If you have issues with the full-screen template, you can download and use the Custom HTML template. This template provides more flexibility for images and allows full control of the template.