Below are some best practices to consider with Push Notifications
Table of Contents
Iterable will automatically track app uninstalls. The methodology is as follows:
- A push campaign is sent to the end user.
- 12 hours later a "ghost push" is sent the user (a ghost push being a silent push that will not alert the user).
- If the ghost push is failed to be delivered to the device due to the app being uninstalled, the app uninstall is then tracked in Iterable.
Migrating GCM to FCM for Android
For Android Push Notification, Google Cloud Manager (GCM) has been depricated in favor of FireBase Cloud Messages (FCM). If you are on GCM, you must migrate to the new system. You can migrate an existing GCM client app on Android to Firebase Cloud Messaging (FCM) using the instructions in this guide. Before getting started, keep in mind the following:
- GCM and FCM SDKs cannot co-exist within an application.
- GCM tokens retrieved via
InstanceID.getToken()will continue to work in FCM without any modification or renewal.
Please follow this Google Guide to complete the migration.
Renewing (Actually Just Creating New) Push Certificates Within Iterable
Your Push Notifications certificates are generally only valid for one year. Once they expire it is the developers responsibility to renew them. You don't actually renew the certificates, you simply create new files and upload them into Iterable.
- Apple should send you an email when your Push Notification certificate is close to expiring.
- It is worth adding a calendar reminder to ensure you know exactly when the certificates will expire.
- The Iterable dashboard will also note your certificates expiration date in the Mobile Apps section.
Please follow the steps in the previous section around creating certificates. Once you have new valid certificates, you can upload them to Iterable and continue to receive push in your app.