The discrepancy you're seeing in delivery is likely related to the fact that you are testing in a dev environment. A user will only be qualified for a push notification if they have a true session within Localytics, meaning the app was opened, push notifications were accepted, and the app was then opened again. In the instance of a dev environment, devices are typically constantly being reset which would render the push certificate invalid for that particular device. In addition, if the user accepts push notifications and then never opens the app again, they would never have a session registered with "push enabled."
Articles in this section
- Why is frequency capping for in-app not working?
- Why are my Apple push certificates not being authenticated?
- What are profiles and how do I use them?
- How do I export a list of all my campaigns?
- If I have multiple buttons in my custom in-app message, how do I ensure Localytics tracks them correctly?
- [VIDEO] Confirm & Test your Push Campaign Setup (4 of 4)
- Can I use emojis for a subject line in an email campaign?
- Why do I still have unread messages in Inbox after reinstalling the app?
- [VIDEO] Create an Audience for a Push Campaign (1 of 4)
- [VIDEO] Schedule your Push Campaign (3 of 4)