Testing your In-App Nativ Campaigns

Introduction

When you are creating your In-App Nativ Campaigns in MoEngage, it is always recommended to test your message display on a wide range of devices to ensure that it is as per your expectations.

After you design messages on the MoEngage dashboard, the actual display on a device may differ from what is being shown on the dashboard because of a variety devices available that your users are using that differ in size, shape and UI.

To help you test the in-app messages easily on your devices, you can leverage the Test Campaign functionality.

Where to find the Test Campaign feature?

In-App Nativ Version 3

If you are using the In-App Nativ Version 3, you can see the Test Campaign functionality on the Step-2 of campaign creation right after you design your in-app message. See the below screenshot for reference - 
Screen_Shot_2020-08-19_at_12.45.18_PM.png

 

In-App Nativ Version 2

If you are using the In-App Nativ Version 2 (older version), you can see the Test Campaign functionality on the last step of campaign creation right before you activate the campaign. See the below screenshot for reference (same for both general in-app and smart trigger in-app) - 

Screen_Shot_2020-08-19_at_12.47.16_PM.png

 

How does it work?

The Test Campaign functionality allows you to quickly see the look and feel of your in-app messages on your app and also test some key functionalities like animations and on-click actions.

To receive an in-app message on your device before activating the campaign for your live users, navigate to the test campaign section during campaign creation and select an attribute to identify you user for testing as shown below -

Screen_Shot_2020-08-19_at_12.43.01_PM.png

The identifier could be any device identifier (like Google Advertising Id, IDFA, push_id) or any user identifier like ID, Email Id, Mobile Number etc. Please ensure that the properties are set for your user in MoEngage before you use these for test campaign. If MoEngage is not able to identify a user with the selected attribute and value, you will see an error message like below - 

Screen_Shot_2020-08-19_at_12.40.41_PM.png

If MoEngage has successfully identifier a user with the selected attribute and value, then you will see a success message on the dashboard like below -

Screen_Shot_2020-08-19_at_12.41.14_PM.png

 

When the Test Campaign is successfully sent to your user, you will receive a push notification on your device as shown below -

Screenshot_20200819-124130.png

On clicking this push notification, your app will open up and you will see the in-app message there as shown below. It may take up to 15 seconds for the message to be shown via Test Campaign (for your live campaigns, we do not introduce any delay) -

Screenshot_20200819-124222.png 

Please note that the push notification is only received in case of Test Campaign functionality and will not be sent for your live campaigns. For your live campaigns, your users will see the in-app message directly after they qualify for the campaign and execute the trigger action.

Test Campaigns ignore frequency capping and display controls and can just be used to test the look and feel of the message.

Test Campaign functionality in Version 2

If you are using the Version 2 (older version) of in-app nativ then chances are that you might be facing some an intermittent issue while using the Test Campaign functionality where the in-app message does not appear on your app after clicking the push notification. This is a known issue and happens because of custom re-direction that you may have implemented inside your app.

To fix this issue, please update your SDK Version to the latest one so that you can use the Test Campaign functionality seamlessly. 

 

Test Campaign functionality in Version 3

With Version 3 of In-App nativ, if you are targeting the older generation of in-app SDK Versions (Android SDK < 10000 and iOS SDK < 6.0.0), then you will have to select the checkbox as shown in the image below - 

Screen_Shot_2020-08-31_at_12.33.44_PM.png

This will ensure that your TEST Campaigns will continue to work on your older generation of SDKs. The recommended approach however is to update the Moengage SDK you have used to the latest version. 

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