Overview

MoEngage In-App NATIV campaigns or In-App Presets is a collection of pre-created In-App campaign templates featuring effective use cases, with an inbuilt help to guide you through the use-case and allow you to create these campaigns in a matter of seconds. Templates or Presets are:

1. Popular and effective use cases advocated by our customer success experts
2. With an in-built help guide
3. Easy to use
4. Created in a matter of seconds

MoEngage offers Native templates and HTML templates.

Template Types

Use different types of templates based on your requirements:

Customizing Native In-App Templates

While using our InApp Native campaigns, there are a few guidelines that need to be followed to ensure that your in-app templates look the best on all devices.

Customizing Images

We recommend our In-App Nativ users upload images of high definition but not exceeding 1 or 2 MB in size. This is because before an In-App message is shown on the device, the image within the message is downloaded from a CDN before being shown to the user. If a user is on a slower internet connection, it might take longer for the image to be downloaded and hence there will be a delay to show the in-app message to this user.

Aspect Ratio of Images

The following are MoEngage recommended aspect ratios of images for each template type -

Accepted image types

For In-App Nativ, you can upload .png, .jpeg, and .gif as images in any of the In-App native templates. Note that for using GIFs in Android In-App Native, you need to ensure that the integration steps mentioned here are done. GIFs are supported by default on the iOS platform.

Image Quality and Size

For In-App Nativ templates, try to use high-resolution images so that they do not distort even on large screens. The higher the image size, the higher the chances of the image failing to download on a device with a flaky internet connection. Use images of less than 2MB in size so as to keep a good balance between image quality and time for download.

Scaling Images as per device dimensions

The In-App messages you create are rendered on devices with different form factors and dpi. As a result, the image that you upload on the dashboard is scaled down or scaled up when it is rendered on devices of different dimensions. For example, you upload an image of dimensions 600*1000 pixels (width * height) on a device for the template - Popup - Image. Now when this message is displayed on a device with width = 320 pixels where the in-app message occupies about 400 pixels width. In this case, we will scale down the image width to 300 pixels and calculate the height basis the aspect ratio of the image (3:5) which is 500 pixels. So the 600*1000 pixels image will be scaled down to 300*500 pixels. This way the image will never break. When images are scaled up or down, it is important to know that we only scale the width and calculate the height basis the aspect ratio of the image so that the image is not distorted when it is displayed.

Background Images

Configure background images for the In-App messages.

1. On the Content tab of step 2 of campaign creation, click Template Settings
2. In the Template background image, use one of the following:
   • Click Image URL and type or paste the URL of the image.
   • Click Upload Image and drag and drop the image or click the upload from the computer the stored image.

Background Color

Background color allows you to add a background to your in-app messages. It can also be removed to make your messages transparent.

1. On the Content tab of step 2 of campaign creation, click Template Settings.
2. In the Background color, select the color.
3. In the Phone Background color, select the color.

Full-Screen Template

Full-Screen Templates occupy the whole screen of the user and are rendered over an opaque background. While using the Full-Screen Template, it is very important to note that you need to use images that have a single color right now and set the background color and tint color should be the same so that the in-app message has the appearance of occupying the whole screen.

All full-screen in-app messages will fill the status bar on “notched” devices.

To create a proper full-screen in-app message, please ensure to do the following (only applicable for Version 3 of In-App Campaigns) -

1. Upload an image of a 3:4 or 3:5 aspect ratio.
2. Set the background color to merge with the image color.

3. Set the overlay color to merge with the background color. After all 3 steps are done, you will see the In-App message on the device as described.

   

   info

   Information Note that on SDK Versions less than 10000 (Android) and less than 6.0.0 (iOS), the Full-Screen Message will be top-aligned and does not occupy the entire screen. On the later SDK versions, MoEngage templates centrally aligned and configured the overlay to occupy the entire device height.

Rating Template

Rating Template is a special template available in InApp Nativ. This allows your end-users to provide ratings for a specific activity inside the app or for the whole app. While creating the rating template, configure the following:

Configure the rating appearance:

Configure the Rating in a user attribute:

Action-based on User Rating

Marketers often have this use case around Rating Pop-ups that if the end-user has rated them greater than 3, they want to take them to App/Play Store. Else they want to take them to a feedback page or take no action.

In our quest to allow marketers to achieve more via MoEngage, we allow you to set Conditional Action basis in which you can decide what you want your end-user to do basis his/her rating. e.g.

Send the user to URL if rating is greater than 3

The comparison operators are inclusive in nature and work as below:

• Greater than 3 refers to a rating value of {4,5}
• Less than 3 refers to rating value for {1, 2}
• Equal to 2 refers to rating value of {2}
• Between 2 and 5 indicate rating values of {2, 3, 4,5}

Supported SDK Versions

Rating In-app is available only for Android SDK version 8.4.00 and above, iOS SDK version 3.9.0 and above. Please update your version for MoEngage iOS SDK and MoEngage Android SDK if you are on versions as mentioned.

Push Notification Permission Template

Push Notification permission templates provide options for users to enable notifications. Configure the template for opting in for receiving push notifications and trigger permission settings for Android or iOS or the permission dialog box for iOS and Android 13 & above.

Use these buttons to add Push notification opt-in actions depending on your use case.

SMS Sign-Up Template

SMS Sign-Up template enables you to request consent from your users to receive the SMS notifications. For more information on compliance for the North America region, refer to SMS for North America Region.

Configure the template for opting in for receiving notification. MoEngage provides two templates for the SMS Sign-Up.

• Fullscreen - SMS Sign-up with image
• Popup - SMS Sign-up without image

Fullscreen - SMS Sign-up with image

While creating the SMS sign-up with the image template ensure you modify the image and text according to your needs and do the following:

1. Configure the legal text. MoEngage provides the following text by default.
   By signing up for text messages, you agree to receive recurring automated promotional and personalized text messages (cart reminders) at the phone number provided. Consent is not a condition to purchase. Msg & data rates may apply. Msg frequency varies. Reply HELP for help and STOP to cancel.
2. Configure the Terms of Service according to your needs.
3. Configure the Privacy Policy according to your needs.
4. Configure the button to receive consent.
   

Popup - SMS Sign-up without image

While creating the SMS sign-up without the image template ensure you modify the text according to your needs and do the following:

Configure the button to receive consent

1. Configure the legal text. MoEngage provides the following text by default.
   By signing up for text messages, you agree to receive recurring automated promotional and personalized text messages (cart reminders) at the phone number provided. Consent is not a condition to purchase. Msg & data rates may apply. Msg frequency varies. Reply HELP for help and STOP to cancel.
2. Configure the Terms of Service according to your needs.
3. Configure the Privacy Policy according to your needs.
4. Configure the button to receive consent.
   

Personalization

You can personalize the content using User Attributes, User Events, Product Sets, Content APIs, and Content Blocks. For more information, refer to:

• MoEngage Templating Language (JINJA)
• Derived Events & Attributes
• Product Sets
• Content APIs
• Content Block

Do the following:

1. Type @ to personalize the content.
2. Click either Data personalization or Content Block.
3. Click the Data personalization tab and from the drop-down, select one of the following
   1. User Attributes

   2. Select one of the following as for alternate (Fallback) to the personalization:

      • No Fallback Choose the option for personalized content. The option results in no alternates when the personalization does not work.
      • Do not send In-App Choose the option where if the personalization does not work, In-App messages are not sent.
      • Replace Text Type or paste the text used when the personalization does not work.
   3. Product Sets
   4. Content API
      • Modify the values of the parameters of the Content API.
4. Click the Content Block
   1. Select the content block to be inserted
   2. Click Insert only the content of the content block.

      info	Information When the option is selected Only the content is inserted The content is disconnected from the content block Any content update in the content block is not reflected in the inserted content.

5. Click Done.

Frequently Asked Questions

1. What happens if an in-app message goes beyond the device height?
   A: If an in-app message when rendered has a height more than the device height then, in this case, the in-app message will not be rendered.
2. Are images mandatory for in-app templates?
   A: No, images are mandatory only for in-app templates which contain images. If images are not provided for the in-app messages with images, they will not be shown on the device.
3. Is text scaled across different device sizes?
   A: Currently, the text is not scaled across different device sizes. So if you specify a specific font while creating the message, the same font size will be used in the in-app message on all devices.
4. Can I remove images from in-app messages?
   A: Currently images are mandatory for in-app messages with images to be displayed on end-user devices.
5. Can I remove the color from in-app messages?
   A: Yes you can remove the color from the in-app message by setting the opacity to 0
6. What happens to in-app messages when the app is in landscape mode?
   A: When the app is in landscape mode, pre-built in-app messages are not shown as of now but HTML In-Apps will be shown if landscape orientation is allowed while creating the HTML In-App.
7. Are in-app messages supported on tablets?
   A: No, we do not support pre-built in-app messages on tablets right now, but HTML In-Apps are supported.