Browser Push Campaigns
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. These notifications will be sent to your customers when they open their browser regardless of whether they're on your actual website.
New customers will be prompted to opt-in 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 opt-in per browser. Browsers specifically stop you from repeating opt-in attempts.
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 opt-in via the above example to achieve two things:
- Prevent the user from not opting in. With AIQ requesting the opt-in first, we can let them choose to opt-in "Later" if for some reason they don't have time or wish to opt-in at that exact moment.
- 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
- Navigate to Settings > Loyalty App > App Features
- On the page, click on the Features tab
- Under the "General" section, there will be a toggle for "Browser notification opt-in (Web-Wallet only)
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.
See Campaign Builder for general information on how to build a campaign.
Notes on the builder:
- you can add a Feature image to your campaign by clicking Add Media
- See what opting into the browser looks like or send yourself a test of the campaign
See Supported Browsers for the latest.
Anonymous browsing
Incognito or private browsing modes are not compatible with browser push.
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 opt-in.
Moving or importing subscribers
Browsers do not support moving or importing subscribers cross origin
Here are common layout guides to follow for push notifications across all platforms:
How many characters are allowed and recommended per platform. Emoji support is available across all platforms 👍 | |
|---|---|
Images | Large Images that appear with the notification. Supported by Chrome on Windows, macOS, and Android. |
Icons | Supported on all platforms. Customizable for Chrome and Firefox. |
Sounds | Not customizable on Web Push. |
Small icons on Chrome for Android that appear in top Notification Center when push is received. | |
Custom buttons that can support different actions or links. |
Since each platform uses a different visual layout, the amount of content that is visible varies.
The following are approximations for how many characters are in a notification based on the browser platform.
Platform | Title limit | Body limit |
|---|---|---|
ℹ️ AIQ Recommendation | ℹ️ 20 | ℹ️ 60 |
Windows: Chrome | ~60 (Chrome 68+) ~40 (Chrome 67 and lower) | ~120 (Chrome 68+) ~150 (Chrome 67 and lower) |
Windows: Firefox | ~40 | ~190 |
Mac: Chrome, Firefox, Safari | ~40 | ~20-80 |
Emojis count as a single character. Simply copy-paste the emoji you want into the message or title. Some limitations on Windows 7 and older Operating Systems.
