Self Handled In-App Template

Introduction

Self-Handled In-App Campaigns leverage the MoEngage In-App Nativ Campaigns and trigger a certain action inside your mobile apps.

You can leverage all capabilities of MoEngage Mobile In-App Campaigns like Segmentation, Event Triggers, Personalization, Delivery Controls and trigger your own app's In-App template or modify your app UI instead of showing a MoEngage In-App template.

Using Self Handled In-App Campaigns

At times, you may want to show your own In-App messaging templates to your user which are not supported by MoEngage In-App campaigns. To do this, you can select the self-handled campaigns in MoEngage and trigger your template when the user satisfies the campaign conditions. The campaign management and campaign performance stats will be maintained on MoEngage for your reference.

Personalization of Content

You can personalize the content of a Self Handled In-App campaign. In step 2 of campaign creation, on the Content tab, type @ in the content where you wish to personalize.

You can personalize the content using User Attributes, User Events, Product Sets, Content APIs and Content Blocks.

For more information, refer to

SelfHandled.gif

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
      1. 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.

App Personalization with Self Handled In-App Campaigns

At times, you may want to personalize your mobile app for a certain segment of users and also visualize how the users are reacting to this app personalization by tracking the Click Through Rate, Conversion Rate, and other performance trends.

With MoEngage Self-Handled In-App Campaigns you can do this.

A few examples of App Personalization are as below -

  • Personalize the background color of your app screen: Try out different background colors for your app screen to boost conversion.

  • Personalize the CTA color of your app screen: Experiment with different CTA colors to boost your click-through rates.

  • Personalize the products in your product carousel for each user: Show personalized products on your category page or home page to boost conversions.

  • Localize the text on your app for different user segments to boost signups: Show localized text on your signup page to boost the number of users who are completing the signup process.

Experiment 2 of the article describes how to set up these app personalization use-cases. You can also configure any experiment apart from these use-cases as required.

SH.gif

 

Setting up Self Handled Campaigns with In-App Nativ

library_add_check

Prerequisites

Ensure that the MoEngage SDK for self-handled is enabled.

To use Self Handled Mobile In-App Campaigns in MoEngage, start creating an In-App campaign as you would normally do and select the self-handled template as described-

Selfhandled.png

After selecting the self-handled In-App template, specify the text that you want to send to your app like below -

SelfHandledContent.png

This is the exact payload that will reach your mobile app when a user qualifies to see this campaign.

After receiving the payload from MoEngage, you can consume it to show your template or personalize your app as required. 

Integration Steps

There are integration steps required to be able to use self-handled In-Apps and track the performance stats for your campaigns like impressions, clicks, and conversions. Follow the below integration steps to start using self handled In-App campaigns -

Android

iOS

These integration steps allow you to consume the data under a self-handled campaign on your mobile app and also pass on performance stats like impressions and clicks to MoEngage to visualize the performance of your campaigns.

Experiment 1: Personalize the background color of your app screen

Hypothesis

Changing the background color of your app will boost conversions by making the UI look more appealing to your users.

Campaign Creation

Start creating an In-App nativ campaign and select the self-handled template on step-2 of campaign creation.

  • Segmentation: Select the set of users for whom you want to change the background color of your app. For example -
    SH_Experiment01.png

  • Conversion Goals: Measure the performance of your campaigns by defining a conversion goal on step-3 of your campaign creation.
    Goal_Exp_01.png

Self Handled Template Data

Your app would need to receive the exact color to update the background color. To send the exact color, you need to add the below text in self handled campaign data - 

{
"moe_element_type": "background_color",
"moe_background_color": "#FBE192"
}

You can change the key names and values as required. This is just a sample.

Integration Steps

On your app, you need to consume this JSON and update the background color as available under the key "moe_background_color" as shown in the image reference in the next section.

Result

The app looks like the following image before and after you run the test.

app_personalization-1.png

 

Measuring the Results of Your Experiment

  1. Click-Through Rate: You can measure the click-through rate from the MoEngage campaign analytics page as shown below to measure if changing the background color increased the number of clicks on this page.

  2. Conversion Rate: You can measure how your experiment has performed by calculating the conversion rate of these users after the experiment was run and before the experiment was run.

Experiment 2: Personalize the CTA color of your app screen

Hypothesis

Changing the color of the main CTA on your sign-up screen will boost sign-ups (conversions) by making the CTA stand out on your app screen.

Campaign Creation

Start creating an In-App nativ campaign and select the self-handled template on step-2 of campaign creation.

  • Segmentation: Select the set of users for whom you want to change the background color of your app. For example:
    SH_Ex_02.png

  • Measure the performance of your campaigns by defining a conversion goal on the step-3 of your campaign creation -
    Goal_Ex_02.png

Self Handled Template Data

Your app would need to receive the exact color to update the background color. To send the exact color, you need to add the below text in self handled campaign data - 

{
"moe_element_type": "button_color",
"moe_button_color": "#753BC3"
}

You can change the key names and values as required. This is just a sample.

Integration Steps

After you receive this campaign from MoEngage, you need to read the key - "moe_button_color" and apply this color to the button on your app screen.

Result

app_personalization-2.png

 

Measuring the Results of Your Experiment

  1. Click-Through Rate: Measures the click-through rate from the MoEngage campaign analytics page as shown below to measure if changing the color of the button increased the number of clicks on this button.

  2. Conversion Rate: Measures how your experiment has performed by calculating the conversion rate of these users after the experiment was run and before the experiment was run.

Was this article helpful?
2 out of 2 found this helpful

How can we improve this article?