If the customer blocks push notifications in the OS, does that mean we have no way of knowing about it, and will we still see them as delivered or sent?
Correct. For push notifications, we're getting the information only from the browser. Since notifications are allowed in the browser, we received the sent/delivered events. But we don't have the OS information that it blocked the push notification.
If the above is true (that is, blocked notifications from the OS come through as delivered or sent), how do we identify customers who have blocked notifications this way?
Since we don't have this information from the customer's OS, identifying active customers based on delivered events becomes less reliable. You can focus only on the clicked/closed events to obtain valuable information about customer behavior and take action accordingly.
What is the expected behavior when the customer blocks push notifications from the browser?
If a customer blocks push notifications in a browser, nothing happens with the Customer Profile within the Bloomreach Engagement platform yet.
If a customer receives another push notification from us, then we're tracking a failed campaign event with status code 410. Based on this status_code,we're setting the current browser_push_notification to null.
When a customer decides to allow notifications again in the settings, the customer needs to be subscribed to notifications once more (this is done via the weblayer by allowing notifications). Then we set the current browser_push_notification value in the Customer Property, and the push notifications start working again and are received by the customer. You can refer to our Browser Push Notifications feature guide for more information on the setup.