“Notifications delivery rate” is a key metric for every push notifications product. So when our system recognizes and confirms a notification as “delivered”, it means it has successfully distributed the notifications using our partnered delivery service.  However, sometimes notification does not get delivered to the individual’s device even when our systems show it as delivered. 

There could be multiple reasons why this happens, below are the major ones: 

  • by blocking notifications in browser settings
  • by blocking notifications specifically on your site
  • by unsubscribing through settings tab on any notification that you send; and
  • by having inappropriate network settings

 A user has to perform any of the following to have unsubscribed under the following conditions:

  •  A user deletes cookie data from his browser
    • by deleting the Cookie data manually from his browser settings
    • by using an application that scans, and deletes cookies and cache data for system maintenance

Deleting cookie data manually can differ from one browser to another. One need to delete cookies manually from respective browser settings. 

Read Manual deletion of cookies in chrome, and Mozilla Firefox.

  • User unsubscribes from your notifications manually
    • by blocking notifications in browser settings
    • by blocking notifications specifically on your site
    • by unsubscribing through settings tab on any notification that you send

Note: You’ll know that a user has unsubscribed only when a campaign is sent out.

Also, Read 
Service Worker(sw.js) file in Push Notifications
Myths around Push Notifications

Follow our Social Media pages.

Facebook|LinkedIn|Twitter

Review us on FinancesOnline.

Website: www.truepush.com
Email: help@truepush.com

(Image credits- Designed by Freepik)