Sending notifications but your users aren't receiving them? This article will walk you through all possible causes step-by-step. Go through them in order below:
1. Access your logs:
Ensure that the notification in question appears in the Push Notifications section of the Progressier dashboard. If it doesn’t, it indicates an error in your notification-sending logic before it ever reached our server.
2. Check your credentials:
If the notification isn’t listed in the Push Notifications section of the Progressier dashboard, verify that your API key and Endpoint are correctly set in your request and that you’re sending valid JSON in the request body.
3. Test your workflows:
In many cases, notifications don’t appear in your logs simply because they were never sent. Double-check your logic and ensure your workflow actually sends a request to our servers. Trigger one manually if necessary.
4. Inspect error messages:
If the notification appears in the Push Notifications section of the dashboard, it means our server received your request. Click on it to inspect its content. If your request failed, you’ll see an error message explaining exactly what went wrong.
5. Watch out for yellow checks:
A yellow check indicates that your request was successful and properly formatted but didn’t match any Connected Device with a push subscription. Below are common reasons for this issue.
6. Notifications not allowed:
The user may have simply not allowed notifications. This isn’t necessarily an issue—no app has a 100% success rate in getting users to opt in to notifications.
7. Fix data syncing issue:
If the email and id columns of the Connected Device table are mostly empty, the issue likely stems from how you’ve connected data. This problem is often intermittent, so avoid drawing premature conclusions. Test your data syncing logic thoroughly—unwrap it from other functions or event handlers, verify it in various scenarios, and test it manually in the developer console.
8. Login/notifications mismatch:
The user may have allowed notifications on a different instance of the app where they haven't logged in. Uninstalling and carefully reinstalling the app, then re-allowing notifications, typically resolves this issue.
9. Understand user errors:
Sometimes, users mistakenly believe they have allowed notifications or misunderstand what "allowing notifications" actually means. Send them a screenshot of the Notification Prompt.
10. Never delete users:
Once you delete a user from the Connected Device table, they will no longer receive notifications. If this is your own device and you forget to also clear your local cache, you may inadvertently block yourself from receiving notifications. As a general rule: never delete devices.
11. Check push status:
If the notification is listed in the Push Notifications section with a grey check, it means your request was successful and had a match.
12. Search devices:
The next step is to open the Connected Device table and check their Push Status. Click on "Search" at the top of the page to find that particular user.
13. Reset permissions:
If the user's status is "Slipping away", "Inactive" or "Not subscribed", their push subscription is no longer valid. This can happen if they have blocked notifications from your app, changed devices, or uninstalled your app. To receive notifications again, they must reset their permissions.
14. Verify device settings:
If the user's status is "Active" AND there is an email/id in the appropriate column AND this matches your request, it means we have successfully delivered the notification to their device and the device itself is deciding not to show it.
15. Try our testing tool:
The Progressier website has a tool that will let you test push notifications on any device. Follow the instructions of our push notification testing tool.
16. Fix your integration:
If the testing tool delivers notifications on your device, but your app doesn't, then there is a problem with your integration:
Double check your service worker exists on your domain.
Ensure the Progressier script/manifest are still integrated into your domain.
Search and delete code snippets that unregister or overwrite the service worker.
Remove other PWA or push plugins installed in your website.
17. Resolve device-level issues:
If neither the testing tool nor your app can deliver notifications on a device, the issue is almost certainly at the device level. Check the following articles for common issues:
👉 Windows
👉 macOS
👉 Android