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
- Can I upload a list of IDFV, IDFA, or other customer info in the Audiences screen to send a push campaign to this custom audience?
- How Can I Update An Expired Push Certificate?
- Why is my app icon showing up as blank or black & white in a push message?
- How should I measure the success of push messaging campaigns?
- Why are my Apple push certificates not being authenticated?
- How do I send a push message to a specific customer ID? With a deep link?
- What setup is required to send a rich push notification?
- What types of files can you include in a rich push? What file sizes are accepted?
- What dimensions should images be in rich push notifications?
- What does a rich push look like to a user running an older version of iOS or a version of an app that doesn’t support rich push?