Do I still need to update my Apple certificate for Safari web push notifications?

The requirement for an Apple certificate for Safari web push notifications depends on which versions of the Safari browser you wish to support.

For Safari 16.4 and Newer

Safari versions 16.4 and above support the standard web push protocol, similar to Chrome and Firefox. For these modern versions, a separate Apple Website Push ID certificate (.p12 file) is no longer required. The unified Web Push configuration in your control panel covers these browsers automatically.

For Safari versions older than 16.4

To send push notifications to users on older Safari versions (before 16.4), you must continue to maintain the legacy Safari configuration. This legacy setup still requires you to generate a certificate from your Apple Developer account and upload it to your Pushwoosh application annually.

In summary:

• If you only need to support Safari 16.4 and newer: You do not need to update the certificate. The standard Web Push configuration is sufficient.
• If you want to continue supporting users on Safari older than 16.4: You must keep your legacy Safari configuration active and update the certificate every year.

How to check for users on older Safari versions

To help you decide whether to continue supporting older Safari versions, you can create a Segment to see how many of your subscribers are using them:

1. Navigate to the Segments section of your application in the Pushwoosh control panel.
2. Create a new Segment.
3. Add a filter condition based on the Device Model default tag.
4. You can configure the filter to include or exclude specific Safari versions (e.g., "Device Model is Safari 15", "Device Model is not Safari 16", etc.) to estimate your audience on older versions.