Test Your In-App Campaign

You can now test your In-app campaign as your users would see it. Initially, you could preview your campaigns and test their UI, but now, you can perform end-to-end tests throughout their run.

 

This feature is available for all trigger types and lets you test the trigger condition, targeting options, and delivery controls of your In-app campaign. 

Testing Your In-app Campaign

To test your campaign, go to the third step of the campaign creation process and click on Test Campaign. 

Configure

To configure your test, input the following details:

  1. Target Platform: Choose Android as your target platform. 
    • Note: Currently, this feature is only available for Android devices. 
  2. Unique Identifier: Select the unique identifier to use for testing your campaign. You have an option to choose between six different user attributes. 



  3. Enter the Unique Identifier: Enter the unique identifier for the device on which you want to test your In-App campaign.

After entering these details, click on Send Test Campaign to proceed further. A push notification will be sent to your device. Follow the steps in the next stage to continue. 

Perform

At this stage, you will see a list of steps that you will need to perform to test your campaign. These steps will depend on the configuration you set while creating your campaign. 

There can be different steps based on the following three trigger criteria - 

  1. On App Open
  2. On Specific Screen
  3. On Custom Event

On App Open 

To perform the test, follow the steps mentioned. For example, in this case, you just need to click on the push notification. Since the trigger is "On App Open", the pop-up should appear as soon as you open the app. 

After performing these steps, click on View Test Results to find out whether your In-App campaign was sent successfully or not. 

On Specific Screen

If you want to test In-App campaigns with the campaign trigger being On Specific Screen, you will see an additional step under Perform these steps

This step will be: Go to screen: The screen you choose

To successfully test this In-App campaign, you must navigate to the screen that you choose to view the campaign. For example, if you want to show the campaign on your Checkout Screen, you must navigate to your app's checkout screen during this process. 

After viewing the In-App campaign, click on View Test Results to proceed.

On Custom Event

This feature also allows you to test the In-App campaigns with custom trigger events. If you have created your campaign using the custom trigger, you will see that as a step while testing your campaign. 

This step will be: Perform trigger: The trigger you selected. 

To successfully test this In-App campaign, you will need to perform the trigger that you have selected to view the campaign. For example, if you want to show the campaign on the "Add to cart" trigger, you must click the "add to cart" button during this process. 

After performing the steps, click on View Test Results to proceed.

 

info

Information

If you do not perform the steps correctly, the test results will display an error and you must start the testing process again.

 

Results

On the test results screen, you will find out if your In-App campaign ran successfully. 

  • If you see a list with green checks under Test Results then your campaign has run successfully. You can also use the testing device to view the In-App campaign and see if all of the visual elements are appearing correctly. 
  • If you see a list with red crosses under Test Results then your campaign has not run successfully. The errors will be listed under the events and you can fix them and Re-test your campaign.
    • Click on the Re-test button on the bottom right-hand side of the pop-up to re-test your In-App campaign.

      Screenshot 2024-03-21 at 1.38.35 PM.png

  • If your campaign trigger was On Custom Event, then you will see another point under Test Results called Perform trigger. If you were able to perform the trigger event, there will be a green check next to the Perform trigger and your test should be successful. 



    • Otherwise, you will see a red cross next to the Perform trigger and an error message will be displayed detailing exactly what went wrong. 

Common Errors 

These are common errors that you might find while testing your campaign - 

 

Error Resolution
Push notification not clicked

 In case you haven't received the push notification, restart the test by selecting "re-test" and ensure that you have configured it correctly by following these steps:

  1. Remove the app from the background.

  2. Activate push notifications - If you're conducting the test on iOS or Android 13 and above, ensure that push notifications are enabled.

  3. Add or update your APNS certificate if it's not there. You can do it from here.

  4. Verify user resolution - Please ensure that the test user exists and you have a device attached for this user.

Screen was not visited

The campaign configuration either has the wrong screen name or the screen was not visited during testing. These could be possible reasons for the issue - 

  1. Correct screen not visited - Please navigate to the screen you configured in step 1 of the campaign creation process.
  2. Screen does not exist - Verify with your developer whether the configured screen name is present within the app.
Context not visited

The campaign configuration either has the wrong context name or the context was not visited during testing. These could be possible reasons for the issue -

  1. Correct context not visited - Please re-test the campaign and navigate to the context you configured in step 1 of the campaign creation process.
  2. Context does not exist - Verify with your developer whether the configured context name is present within the app.
Trigger action not performed

The campaign configuration either has the wrong trigger action or the trigger action was not performed during testing. These could be possible reasons for the issue - 

  1. Custom event trigger action not done - Please re-test the campaign with the chosen custom event(s) to trigger the in-app display.
  2. Trigger action done on the incorrect screen - Please execute the chosen custom event on the screen “{screen_name}” to trigger the in-app display.
  3. Trigger action done on the incorrect context - Please execute the chosen custom event on the context “{context_name}” to trigger the in-app display.
  4. Incorrect event attributes - Verify the {attribute_name}" event attribute/s that has/have been configured. The attribute may either not exist or be incorrect."
Trigger time not executed

Trigger time not executed - 

The configured trigger time has not been waited for. Please wait [5 seconds] on the selected screen for the campaign to trigger. Please note that a delay time of less than 60 minutes is supported within campaign testing.

Campaign not visible

Below are the reasons why you might not be seeing your campaign. Please resolve them and re-test the campaign:

  1. showInApp() method not called on the opened screen: The screen that you opened during testing does not have the "showInApp" method, a necessary component for the campaign to appear on the screen. Configure it by following the steps mentioned here for Android and here for iOS.

  2. showNudge() method not called on the opened screen - The screen that you opened during testing does not have the "showNudge" method, a necessary component for the campaign to appear on the screen.
  3. getSelfHandledInApp() method not called on the opened screen - The screen that you opened during testing does not have the "getSelfHandledInApp" method, a necessary component for the campaign to appear on the screen. 

  4. This nudge campaign was displayed at wrong position({nudge_position}). Please make sure correct nudge position is configured at sdk.
  5. Delivery Errors - see link

 

 

 

 

Previous

Next

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

How can we improve this article?