- Please verify you followed the Push integration guidelines for iOS here
- Please verify you followed the Push integration guidelines for Android here
PUSH TESTING PROCEDURE WITH LIVE CAMPAIGN
(not using the Test mode)
If you are a developer and have just finished implementing Push notifications into your code, please follow the below testing procedures:
-
After a fresh install of your App, make sure to have at least a couple of App sessions. You can do this by launching your app for the first time, then backgrounding the app and waiting 30 seconds (default session timeout period). During this time you can confirm that you have enabled Push Notifications from Settings (if iOS). Once confirmed, you can Launch the app for a second time and then close your session. With SDK versions prior to 3.8, Push Tokens/Registration IDs were not being uploaded to the Localytics backend for registration until a users second session. This would cause issues when users were performing Push tests after only 1 session. Therefore by following these instructions, you can guarantee the Push Token/Registration ID has been updated.
-
After your second app session, allow roughly 15-20 minutes for the Push Token/Registration ID to update and register in the Localytics backend
-
Create a Push Campaign in the messaging dashboard and Send
-
If you still have not received your Push Notification, enable logging for your platform to make sure your device is receiving a Push Token:
Android
iOS
AUDIENCE RELATED
If you have verified that your Push integration is correct and you are inquiring about a Push Campaign that was sent out successfully, however your particular device did not receive the Push Notification, then it maybe due to your Audience conditions and when this data gets updated on our backend.
For example, when using Profile conditions. Profiles can change based on actions in your app, however when the actual data uploads to our backend will depend on when Upload() is called in your app. Many a times, Upload() is not called between when a users Profile changes and when they exit the app. Therefore the Profile value will not get updated on our backend until the user comes back to the app and has their next session which will invoke an Upload(). This creates a situation where you think you've qualified for a certain campaign, but really have not.
Other common reasons for failing to deliver a message include:
-
APNS/GCM do not guarantee delivery. Messages can ultimately be lost in delivery inside the APNS/GCM pipeline because of network conditions.
-
Devices can be offline for an extended period of time.
CREATIVE RELATED
If you design a push message creative, and do not have any content in the body of the message, it will be sent as a silent push. In this scenario, no alert/notification will be displayed on the users device and campaign-level metrics will reflect that. To successfully send a regular push message, be sure to provide a message body as outlined in the image below.
