In-App Notifications Integration Validation

This article explains InApp Notifications Integration validation manually in a stepwise manner.

What is to be validated?

To check if the In-app campaigns are displayed on the app and the CTA buttons are working as expected.

How to validate?

  • Create an in-app campaign for your ID and on-screen launch.

  • Send a test campaign to your device and check for the in-app notification display (on sending a test you will receive a push notification on the device and on clicking this a random page opens on the app and the in-app is displayed). If failed, check for the failure reasons.

  • Complete the campaign creation, and turn off the delivery control. The in-app should start reflecting on your app in 15-30 mins.

  • While creating an in-app, add the redirection by selecting the navigation under add action.

  • Select the navigate to Screen option and select a screen from the dropdown. On receiving the notification, click on it and the screen selected in the dropdown should open on the app. Add the KV pairs if any. (For IOS you can Paste the screen name)

  • Select the deeplinking option, and add the URL. On clicking the notification, the user has to be redirected to the exact portion of the app intended. (Add the KV pairs if any)

  • Select the Richlanding option, and add the URL. On clicking the notification, the user has to be redirected to the web.

  • Once the campaign is sent out, the campaign stats should show the impressions and clicks.

Success Criteria

  • In-App notification has to be displayed on the device
  • The intended redirection has to be achieved
  • Once the campaign is live, the notification impressions and clicks should be recorded.

Potential Issues and Solutions

If InApp is not working, targeting users will not be possible other than through the push channel. To fix this InApp-related issue, please check the Android and iOS docs.




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

How can we improve this article?