Legacy: Browser Push Campaigns

what are browser push notifications? also known as web push notifications, browser push notifications are notifications or messages that can be sent to your customer via desktop or mobile devices on a desktop they look like alert notifications that pop out from the top right of the screen and on a mobile device, they look similar to native app push notifications and are extremely effective these notifications will be sent to your customers when they open their browser regardless of whether they're on your actual website how can i use browser push notifications? browser push notifications are a great option for shorter form copy like reminders that there's a discount waiting for them, abandoned cart campaigns, or adding a link to your e commerce page to let people know about new products that are available how do i turn browser push opt in requesting on/ off? you don't have to do anything! new customers will be prompted to optin to browser push notifications when they first open their digital wallet please keep in mind that we only get one chance to ask customers to optin per browser browsers specifically stop you from repeating optin attempts if you would like to turn optin requests off for browser push, you may do so under the "configure aiq > brand settings > wallet settings dropdown > then flip the toggle "hide browser notification optin" to off once the user clicks allow an additional pop up will appear that the user has to click to allow these types of notifications please note that we must ask the user to optin via the above example to achieve two things 1 ) prevent the user from not opting in with aiq requesting the optin first, we can let them choose to optin "later" if for some reason they don't have time or wish to optin at that exact moment 2 ) browsers only allow requests after a user gesture this is the scalable/ compliant long term approach to browser notifications see mozilla reference you should only request consent to display notifications in response to a user gesture (e g clicking a button) this is not only best practice — you should not be spamming users with notifications they didn’t agree to — but going forward browsers will explicitly disallow notification permission requests not triggered in response to a user gesture firefox is already doing this from version 72, for example, and safari has done it for some time how do customers opt out of browser push notifications? in the browser you're opted into, click on the icon to the left of the url select the dropdown to the right of notifications and select block optout instructions are specific to the browser the user opted into how to build browser push notification campaigns head to your campaigns page, click create new campaign, and select the newly available add browser add your subject, message, & link if applicable notes on the builder you can add a feature image to your campaign by clicking add media you can add personalization macros, emojis, and discounts the same way you would in an sms campaign see what opting into the browser looks like or send yourself a test of the campaign what browsers and platforms support browser push notifications? see supported browsers for the latest anonymous browsing incognito or private browsing modes are not compatible with browser push how your sending domain works to perform browser notifications, aiq sends messages out via a service this service is "subscribed" to by each person that opts into browser push once a user subscribes, you cannot transfer their optin moving or importing subscribers browsers do not support moving or importing subscribers cross orgin