June 15, 2020 Faith Arias

Push Permission Changes at Google Chrome

Google is always keen on improving the experience of its users and modifying how and when push notifications are displayed is one of its key efforts. As is usually the case, there are several changes that are either being discussed or are already being implemented, especially concerning prompts. So, here is the rundown:

– Potential permission prompt updates.
A keyword in Google’s efforts to modify permission prompt has been so-called quietness. What this means is that Google is playing with the idea of changing how push notifications are being presented to the user. Instead of simply implementing blanket changes to how push notifications are being displayed, Google mainly wants to impact websites with low acceptance rates on their prompts. The reasoning is that if push notifications are frequently denied, they are likely a factor that negatively contributes to user experience. In these cases, Google will display a quiet notification prompt instead.

– What could this mean?
Providers of effective push notifications such as PushPros have always made sure that the offer the highest-quality notification services to their customers. Because of this, the push notifications that users are seeing as a result of PushPros services are unlikely to experience a noticeable difference from these changes. In fact, removing many of the push notifications that negatively impact user experience may even benefit push notifications that are done right, as users come to perceive them more as a generally positive service. The users that are switched to quiet notifications because they deny opt-ins out of habit already will also not change the effectiveness of well-implemented push notifications.

– How to adapt to this.
Again, if your opt-in rates are high then these changes are no cause for concern. If you are still wondering about which options you may have, a good way to improve the effectiveness of your notifications is to implement a custom opt-in prompt. A custom opt-in prompt will be shown to your users before they are presented with your native prompt. If they deny the custom opt-in, then they will never see your native prompt and will not count against the acceptance rate of your website. The users who do accept the custom opt-in prompt, however, are far more likely to also accept your native prompt when they see it after accepting the custom one.

Another option is to change when and how your native opt-in prompt is being displayed. You could determine that it only shows after the user visits a few pages on your website, because this way the user is more likely to be really interested in your content. Your native opt-in prompt could also display on a specific page on your website, after the user has spent a set time browsing your site or scrolled down a pre-determined percentage of a page.

These adaptations can increase the likelihood that your opt-in prompt will only be shown to users who are truly interested in your service, which can maximize your successful opt-ins. There is a lot you can do by playing around with this type of logic, both for custom and native prompts.

– Ultimately, no cause for concern.
To sum this up, quiet notifications are no cause for concern for most push notifications out there. The changes are intended to eliminate poorly implemented or abusive push notifications, as well as remove notifications for users who habitually decline them anyway. As a result, these changes can provide a great incentive for developing push notifications further and also increase the effectiveness and reputation of the good kind of push notifications out there.