Recently, you may have noticed more and more websites requesting your permission to enable push notifications. Used effectively, they can be an incredibly valuable tool for increasing audience engagement, particularly amongst desktop users. Unfortunately, in our experience, most businesses don\u2019t know how to use them effectively.<\/p>\n\n\n\n
As a result, they end up annoying their audience rather than compelling them. Let\u2019s talk about how you can avoid making the same mistake. Here are five best practices for push notifications on your website. <\/p>\n\n\n\n
Many websites request permission the instant <\/em>a user lands on the site without providing any context as to why <\/em>it should be granted. This is among the most common website notification mistakes. It can also be one of the most damaging. <\/p>\n\n\n\n With the release of Google Chrome 80 last month<\/a>, the browser has started blocking websites that engage in this behavior. As if that\u2019s not enough of an indication of how Google feels, it outright states in its developer best practices guidelines<\/a> that this is the worst thing you can do. You need to provide users with context and value.<\/p>\n\n\n\n Instead of immediately foisting a permission request on your audience, provide them with some incentive, and send them a prompt when they\u2019re likely to be most engaged with your site. <\/p>\n\n\n\n Just as mailing lists benefit from segmentation, so too do website notifications. Most website push plugins and platforms provide a wide range of analytics data on how and when users engage with the notifications you send. You can use this information, as well as site activity metrics, to more effectively target and personalize your messaging.<\/p>\n\n\n\n Segmentations you should consider include:<\/p>\n\n\n\nPersonalize Everything<\/h2>\n\n\n\n
Don\u2019t Overdo It<\/h2>\n\n\n\n