{"id":1748,"date":"2020-01-09T16:46:57","date_gmt":"2020-01-09T11:16:57","guid":{"rendered":"https:\/\/pushalert.co\/blog\/?p=1748"},"modified":"2020-01-09T18:14:11","modified_gmt":"2020-01-09T12:44:11","slug":"upcoming-changes-in-chrome-notification-permission-prompts","status":"publish","type":"post","link":"https:\/\/pushalert.co\/blog\/upcoming-changes-in-chrome-notification-permission-prompts\/","title":{"rendered":"Upcoming Changes in Google Chrome Web Push Notification Permission Prompts"},"content":{"rendered":"
\"Upcoming

Upcoming Changes to Web Push Permission Prompts in Chrome 80<\/p><\/div>\n

Google Chrome and Mozilla Firefox have both announced changes to push notification permission prompts on their respective browsers coming early 2020.<\/p>\n

While Firefox is moving towards a user interaction based permission model<\/a>, Chrome is looking into user behavior. In this post we are detailing our recommendations and any changes (if required) to the web push opt-in prompts.<\/p>\n

Upcoming changes in Chrome Web Push Notification Permission Requests<\/h2>\n

Google has decided to go with a behavior based approach to handling permission requests on Chrome. Starting with Chrome 80, for users who generally block notifications and for sites that have a very low permission acceptance rate<\/strong>, Chrome will show a quieter permission prompt, which you see below.<\/p>\n

\"Quieter

Quieter Prompt for Very Low Permission Acceptance Websites<\/p><\/div>\n

For the rest of the sites that have good opt-in rates, the normal native opt-in flow will continue as it does today (below).<\/strong> Google will be sharing more on opt-in acceptance data later in Q1 2020.<\/p>\n

\"Chrome

Chrome Native Web Push Permission Request<\/p><\/div>\n

PushAlert is making it easy to stay ahead of these changes<\/h2>\n

The best way to keep a healthy opt-in rate is to use a 2-step Opt-in. Therefore, we are recommending all users to switch to a 2-step opt-in theme.<\/p>\n

The soft-ask approach not only improves user experience, but also offers context as to why users should subscribe to push notifications. A 2-step opt-in will greatly improve your overall acceptance rate as the native opt-in won’t be blocked even if people deny the soft ask.<\/p>\n

We already have three, 2-step opt-in mechanisms in place which you can enable from the dashboard. These can be used separately or together on the same site as well:<\/p>\n

    \n
  • 2-Step Opt-in Themes<\/strong> – You can find 4 different themes under Settings > Opt-in Box (Box, Wide-Box, Bar, Native Alike). You can customize the text, icons, colors as well as position of these themes to suit your website.<\/li>\n
  • PushAlert Subscription Bell (Widget)<\/strong> – You can also enable the widget, which too is completely customizable from colors to position (Settings > Widget).<\/li>\n
  • Subscribe Button<\/strong> – You can also ask users to subscribe using custom HTML buttons or even a link on your website using our JS API.<\/li>\n<\/ul>\n

    What you need to do<\/h3>\n

    If you were using 1-click opt-in earlier, you should switch to a 2-step opt-in. You can use any of our 2-step Opt-in (Soft-ask) themes including a slide in Box, a Native Alike theme, a centered Wide Box and a Bar. You can configure these from Settings > Opt-in Box. You can also check their previews before applying them. If you continue using the native prompt (1-click), you may risk the prompt being blocked by Chrome and Firefox.<\/strong><\/p>\n

    If you are using any of our 2-step mechanisms, then you are good and no changes are required.<\/strong><\/p>\n

    We believe these changes will lead to better push notification acceptance rates and higher click through as well. We are also working on adding more customizable opt-in themes in our next update. Stay tuned for our product updates.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Google Chrome and Mozilla Firefox have both announced changes to push notification permission prompts on their respective browsers coming early 2020. While Firefox is moving towards a user interaction based permission model, Chrome is looking into user behavior. In this post we are detailing our recommendations and any changes (if required) to the web push […]<\/p>\n","protected":false},"author":3,"featured_media":1755,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[35],"tags":[184,207,203,149,205,204,28,206],"_links":{"self":[{"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/posts\/1748"}],"collection":[{"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/comments?post=1748"}],"version-history":[{"count":6,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/posts\/1748\/revisions"}],"predecessor-version":[{"id":1759,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/posts\/1748\/revisions\/1759"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/media\/1755"}],"wp:attachment":[{"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/media?parent=1748"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/categories?post=1748"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pushalert.co\/blog\/wp-json\/wp\/v2\/tags?post=1748"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}