Push Reachability

Push reachability provides the number of reachable users via the Push channel in a segment. Push reachability number is required to decide whether to choose the Push channel for sending a campaign if your goal is to reach users via the best-performing channels.

This article explains how the reachability of the Push channel is derived. For the Push channel, it also explains the reachability of respective platforms (Web, Android, iOS). This article also lists the parameters considered to calculate reachability for users reachable via Push. There is a list of reasons why the users could not be reachable via the Push channel and potential solutions to convert the non-reachable users to reachable users.

User and Platform reachability - Push Campaign

By using the Push channel in a campaign users can be reached on 3 types of devices i.e. Web, Android, and iOS. The push campaign will allow to reach users via push notifications and the reachable user count will be the number of users that are eligible to receive Push notifications.

push platform wise.gif

How is user reachability calculated for Push campaigns?

Push reachability is derived by the given parameters -

  1. Users should have at least one active device.
    • In the case of iOS, the app should be installed on the device, and the device should be opt-in for push notifications.
    • In the case of Android, the app should be installed on the device, and the device should not be opt-out for push notifications.
    • In the case of the Web, the user should have visited the website once and must Opt-in to the browser permission
  2. Push token for this device should exist.
  3. For reachability on the different iOS & Android, at least one active device for the respective platform should exist, and the device should have the app installed.

Based on the above parameters system generates reliability codes for all platforms. The reachability codes are stored in User Attributes 'Reachability Push Android', 'Reachability Push iOS', and 'Reachability Push Web'. The user is considered to be reachable on the respective platform if the attribute value (reachability code) in these attributes is 200 and 201.

MoEngage also updates users' reachability based on feedback from silent Push (run periodically if the setting is ON) or Push notifications.

Reachable users across different channels:

Reachability by Channel.gif

Push reachable users across different platforms:

Screenshot 2024-03-05 at 1.27.11 PM.png

How to analyze and find reasons for users' non-reachability?

Step 1: Go to Analyse and select "Users" to do the user analysis

Step 2: Select the user attribute in the User Properties section (either from Push reachability Android, Push reachability iOS or Push reachability web)

Step 3: Below in the User Analysis Options select Analysis type as "Distribution" and click Apply button

Step 4: Analyse the generated graph and look at the reasons for non-reachability for Push channel along with the distribution count

push video1.gif

Similarly, you can do this for all the 3 platforms (Android, iOS, Web) together or for other platforms individually.

Potential solutions to solve users' non-reachability problems

Reachability Push Code (All devices) Reachability Description What could be a potential solution to solve this?
202

Not reachable due to Opt-out.

This is the reachability value for any user who has opted out of receiving push notifications on all of their Android devices.

These users are no longer considered reachable and will not be targeted for campaigns. 

To exclude opted-out users and thereby have more accurate delivery reporting, please reach out to your Customer Success Account Manager.

Targeting inbound campaigns (In-Apps, Card, On-site) to lure the user to opt-in by redirecting to the permissions setting page. As user needs to modify the permission to be reachable.
300

No device found

User will not be reachable if the device is not found for the user. The reason for the device not being found is when just the user creation has happened but any device is not present for that user. Such type of user can be created in the following ways:

  • If the user is created using user import using a file
  • If the user is created using S2S API call (Server call)
Using outbound email, SMS or WhatsApp campaign target these users to install the app and sign up through any device using the same credentials.
403

Not reachable due to App uninstalled

Any user who is not reachable due to app being uninstalled

An outbound email, SMS or WhatsApp campaign can be targeted to these users using suitable content (Offer, FOMO, etc) to make them install the app again.
404

Not reachable due to Push ID not found for the app

Any user who is not reachable due to Push ID not found

Check this with your app development team if they have not opted for the MoEngage solution to generate a Push token. The problem could be with the calls made to FCM/APNS for token generation or authentication.
 
409

Not reachable due to invalid push ID

Any user who is not reachable due to an invalid push ID

Note: Above solutions are some of the potential solutions, which may or may not result in the expected result/success.

Example:

If you want to make all the push unsubscribed users to subscribe for your push notifications, you can do it in this way:

Step 1: Select the section in the pie chart that denotes Push unsubscribed users

Step 2: Create a segment or take action by choosing a Specific channel and Delivery type to target the Push unsubscribed users

Step 3: Configure the content on the campaigns page

push video 2.gif

Similarly, you can target users with other reasons who are not reachable through the Push channel.

Previous

Next

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

How can we improve this article?