Is your push notification delivery rate under 100%? If yes, it’s okay, and here’s why.
Push Notifications resonate with the speedy and real-time delivery of brand communications. But, often, there are instances where not all subscribers receive the notifications you send or schedule for sending.
In this post, we’ll be explaining the reasons why your push notification delivery rate cannot be 100%, and what we have implemented from our end that’ll help you understand why your delivery rate is lower than you expected, at any point in time.
1) The browser is not open on the device
Web push notifications appear on a subscriber's screen (on both desktops and mobile web browsers) when the browser from which they opted-in, is open. This means that even if your subscriber is browsing other websites, they will receive your notification real time. But, if the browser itself is not open, they will only receive your notification when they reopen it.
2) When other site data is cleared in Chrome
When users clear other site data from Chrome, the service workers are uninstalled. When this happens, your website won’t be able to send push notifications to that particular subscriber, resulting in a lower delivery rate.
3) The user has disabled background App activity
Within Operating Systems, people can switch off background refresh for apps. One reason could be to save the mobile battery usage. And this can also forcefully disable the Chrome or Firefox App. This leads to the GCM neither overruling the token nor notifying the Chrome server.
4) Network problems disconnect GCM and the user
Many a times, users are not connected to the internet for a long time. The reasons could be many, from being in areas without network coverage to avoiding roaming charges. When this happens, the device sends heartbeats at an interval of 28 minutes on the cell phone network and 15 minutes on WiFi (GCM’s idle socket connects an Android device to the Google servers).
If this heartbeat doesn’t reach the GCM server, Google continues to re-attempt the connection. So, if the push notification user is disconnected from the internet for a long duration, GCM can neither deliver the notifications nor mark them as dormant. This can either delay the delivery of the notifications or not deliver them altogether.
5) Browser App uninstalled
When a user uninstalls a browser app, there’s a delay in GCM tagging that device as non-functioning. This results in the notification being sent to the GCM, GCM attempting to send it to the device, and failing at it.
6) Notification expires before reaching the end user
If a user has either uninstalled the browser app, disabled background activity (mobile devices) or has been disconnected from the Internet for too long, and you’ve set an expiry to your notification, then chances are that the notification will not be attempted to be delivered once that specific time lapses.
Identifying these problems, we’ve established the Ghosting system. In this feature, our algorithms predict and identify inactive push notification users for each Wingify Engage (formerly PushCrew) account, that is, subscribers that will never receive your notification due to any of the reasons stated above. This is followed by our system marking them as inactive or “Ghosts”. Please remember that you won’t “lose” subscribers with this. Even after our system has marked certain subscribers as “Ghosts”, we will continue to attempt delivering your messages to them, until they are marked as unsubscribed.
This way, you’re only charged for the number of active push notification subscribers.
Need more help?
For further assistance or more information, contact Wingify Support.