Help Center

Commonly asked questions related to Web Push campaigns

Campaign Creation

Your dashboard comes with a highly-intuitive 6-step campaign creation interface that enables you to customize, personalize and test your messages with great ease. Here are a few questions that are frequently asked by our clients:

1. Which OS & Browsers support the Layouts available in my dashboard?

You can leverage the following layouts to create highly effective Browser Push Notifications:

LayoutPersonalized ImageButtonsPersonalized Title & MessagePersonalized Icon
TextNoYes (2)YesYes
BannerYesYes (2)YesYes

Both Layouts are compatible with all the Browser-OS combinations that support Web Push Notifications.

Here's a Browser x OS compatibility map to help you plan your Web Push engagement strategy as per each Segment's technological preferences:

Device OSBrowsers that support Web Push
Android (Mobile + Tablet)Chrome 50+, Firefox 44+, Opera 46+
WindowsChrome 48+, Firefox 44+, Opera 42+, Edge 17+
iOS (Mobile + Tablet)Safari 16+ (If PWA is created)
Mac OS XChrome 48+, Firefox 44+, Opera 42+
Max OS 16.4Safari 16, Chrome, Firefox
LinuxChrome 48+, Firefox 44+, Opera 42+

Here's a Layout Element - Browser x OS compatibility map to help you understand the limitations of all major OS and browsers preferred by users to receive Web Push Notifications:

Browser x OSTitle Char. LimitMessage Character LimitCustom ButtonsIconBanner Image
Chrome x Android4749 (95 if no Banner Image)YesYesYes
Chrome x Windows 957126YesYesYes
Chrome x Windows 10+67159YesYesYes
Chrome x Mac OS X2727NoYes (not supported from 16+)No
Firefox x Android48555NoYesNo
Firefox x Windows 954200NoYesNo
Firefox x Windows 10+52135NoYesNo
Firefox x Mac OS X3742NoYes (not supported from 16+)No
Safari x Mac OS 16+4090NoNoNo
Safari x iOS 16.4+4090NoNo (PWA icon only)No

However, given the varying number of characters supported by each Browser-OS combination, we've compiled a few neutral guidelines to ensure that your message is visible across most: Web Push Text Guidelines.

2. How can we target specific devices and browsers?

You can easily create Web Push Notifications targeted at users with specific device, browser or OS preferences by grouping them into a Segment. As shown below, this can be achieved by adding parameters under the section, Technology while creating the segment.


Click to enlarge


Detailed read: Step-by-step Guide to Creating Segments

3. How can I send a notification as per each user's timezone?

You can easily schedule a Web Push Notification for delivery in your user's timezone by selecting One-time as the Campaign Type at Step 2: When.


Click to enlarge

As highlighted above:

Step 1: Select Later against Delivery Time

Step 2: Specify the delivery date-time, select In User's timezone from the last dropdown and you're all set!

Step 3: Continue building your campaign..

4. How can I engage users in multiple segments through Web Push?

You can easily combine multiple segments under Step 1: Audience while creating a campaign.


Click to enlarge

As highlighted above:

Step 1: Select Send to users in multiple segments and/or... against the field, Audience Type

Step 2: Select the logic by which you'd like to combine the segments: Send to only those users who are included in ALL Segments OR Send to users in ANY of the selected Segments

Step 3: Continue building your campaign

Campaign Delivery, Failures & Queueing

Here are a few questions that are frequently asked by our clients:

1. What happens when Web Push Notification is sent to an offline user?

All Web Push Notifications are delivered through VAPID at WebEngage. In cases where a user is offline, the notification is qeued for delayed delivery as per the Queueing Duration specified while creating the campaign.

  • If a delivery window opens up within the specified duration (user comes online), then we'll deliver the message to them. If not, then the message will be dropped and will be counted towards the campaign's Failures stats with the reason - Other Failures.

  • If Queueing is disabled while creating the campaign, then the message will fail to get delivered, indicated by the reason, Other Failures (under Web Push Campaign Overview).

2. Why do Web Push Notifications look different on Chrome x Windows 10?

With the release of Chrome v68 in July 2018, Google Chrome now supports the native notifications system of Windows 10. This means that all users who have opted-in to your channel through Chrome v68+ through a Windows 10+ device will now experience Web Push Notifications like the visual below.


Click to enlarge

  • The notification will be displayed above the taskbar and will also appear in the Windows Action Center until a user dismisses it or clicks on it.

  • The banner image’s height will be cropped to 360px and will be displayed above the icon & text (120px is cropped from the bottom of the image).

  • The custom buttons will appear side-by-side, as shown above.


Detailed read: Image and Text Guidelines for creating Web Push Notifications

3. Why do some Web Push Notifications fail to get delivered?

Web Push Notifications may fail to get delivered to a few users for various reasons like, the user has unsubscribed, the campaign was triggered through a Journey for a user who is not reachable on the channel, and so on.


Detailed Read

Web Push Delivery Failure Reasons

Analyzing Failures for a Web Push Campaign

4. Why do some Web Push Notifications get Queued?

The term, Queued indicates the number of messages that have been sent to a campaign's target audience but are currently lined up for delayed delivery. This usually happens when DND Hours or Frequency Capping settings are applicable for a user.


Detailed Read

How Delivery Time is Determined for Messages that get Queued

Analyzing Queued Messages for a Web Push Campaign

Please feel free to drop in a few lines at [email protected] in case you have any further queries or feedback. We're always just an email away!