Testing In-App Campaign


MoEngage recommends testing your message to ensure that the message is displayed on a wide range of devices according to your expectations.

The messages on the MoEngage dashboard might be different from the actual display on a device due to the variety of devices available that your users are using.

Use the Test Campaign to help you test the In-App messages easily on 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 Step-2 of campaign creation right after you design your In-App message. 

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) - 


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 your user for testing as described:


The identifiers are any device identifier (like Google Advertising Id, IDFA, push_id) or any user identifier like ID, Email Id, Mobile Number, and so on.



Ensure that the properties are set for your user in MoEngage before you use these for the test campaign.

If MoEngage is not able to identify a user with the selected attribute and value, the following error message is displayed:


If MoEngage has successfully identifier a user with the selected attribute and value, the following success message is displayed:


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


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) -




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 Version 2 (older version) of In-App nativ then chances are that you might be facing some intermittent issues 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, update your SDK Version to the current version 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 described:


This ensures 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?
2 out of 3 found this helpful