Skip to main content
You should test campaign messages to ensure they appear as expected on various devices. Message previews in the MoEngage Dashboard might not always match how they look on an actual device because of the many different devices available. The Test Campaign feature helps you test In-App messages on the devices you choose.

​
Find the Test Campaign Feature

​
In-App Nativ Version 3

If you use In-App Nativ Version 3, you can find the Test Campaign feature in Step 2 of campaign creation after you define your In-App message. TestingInApp_01.png

​
In-App Nativ Version 2

For In-App Nativ Version 2, the Test Campaign feature is available on the last step of campaign creation, before you publish the campaign. This applies to both general and event-triggered In-App messages. Screen_Shot_2020-08-19_at_12.47.16_PM.png

​
How to Test Your In-App Message

The Test Campaign feature lets you see your In-App messages on your app and test key functions like animations and on-click actions. To receive an In-App message on your device before activating the campaign for your live users:
  1. Navigate to the Preview in-app section during campaign creation.
  2. Select an attribute to identify your test user, as shown below.
TestingIn_App_02.png You can identify users by any device identifier (for example, Google Advertising ID, IDFA, or push ID) or any user identifier (for example, ID, Email ID, or Mobile Number).
Ensure that you set the properties for your user in MoEngage before you use them for a test campaign.
When MoEngage attempts to send the test campaign: After MoEngage successfully sends the test campaign to your user, you receive a push notification on your device, as shown below: Screenshot_20200819-124130.png Tap this push notification to open your app and see the In-App message, as shown below. It can take up to 15 seconds for the message to appear through a test campaign. Live campaigns do not have this delay. Screenshot_20200819-124222.png
MoEngage sends this push notification only for test campaigns. Your live campaign users see the In-App message directly after they meet the campaign criteria and perform the trigger action.
Test campaigns ignore frequency capping and display controls. They help you test only the look and feel of the message.

​
Troubleshooting Common Test Campaign Issues

​
In-App Nativ Version 2

If you use In-App Nativ Version 2 (older version), you might experience intermittent issues where the In-App message does not appear in your app after you tap the push notification. This known issue occurs due to custom redirection that you implemented within your app. To fix this, update your SDK to the current version so you can use the Test Campaign feature seamlessly.

​
In-App Nativ Version 3

This ensures that your test campaigns work on your older SDKs. However, MoEngage recommends updating your MoEngage SDK to the latest version. For more information on the In-App SDK, refer to In-App NATIV.

​
Next Steps