EngageLab WebPush is a professional web push messaging service platform with an average daily message volume exceeding tens of billions. WebPush supports browser push notifications on Windows, macOS, and Android platforms. The SDK is easy and quick to integrate, push channels are fast and stable, the open API interfaces are powerful, flexible, and easy to use, and the web console supports operational features such as notification creation, performance analysis, and troubleshooting.
Note: Microsoft Edge (updated in 2019), Opera, Samsung Internet, Yandex, and UC Browser are all Chromium-based browsers and are labeled as Chrome in EngageLab.
Note: Internet Explorer no longer receives feature updates. Microsoft has shifted browser development to the Edge platform.
Browser Version Support
| Browser |
Windows |
macOS |
Android |
| Chrome |
Chrome 42+ |
Chrome 42+ |
Chrome 105+ |
| Firefox |
Firefox v44+ |
Firefox v44+ |
Firefox v104+ |
| Apple Safari |
/ |
Safari v11.1+ |
/ |
| Opera |
Opera v29+ |
Opera v29+ |
Opera Mobile v64+ |
| Microsoft Edge |
Edge v17+ |
Edge v17+ |
/ |
Analytics Support
App-Level Analytics Features
| Analytics Feature |
Feature Description |
| Data Overview |
Supports real-time message data analytics at hourly granularity, with a comparison of today’s and yesterday’s data trends.Supports viewing yesterday’s push conversion funnel data, including delivery rate and click-through rate.Supports viewing the latest device notification permission opt-in rate data.Supports viewing historical push conversion trend data by browser.Supports viewing historical push message loss analytics data by browser and stage. |
| Message Push Analytics |
Supports viewing historical push data by browser and message type.Supports viewing data such as message delivery rate, click-through rate, valid target count, send count, delivery count, display count, and click count within a custom time range by day or month. |
| Push User Analytics |
Supports viewing historical push user data by browser.Supports viewing data such as new push users, online users, active users, and uninstalled users within a custom time range by day or month. |
Message ID-Level Analytics Features
| Analytics Feature |
Feature Description |
| Message Push Analytics |
Supports push conversion analytics reports for two basic message types: notification messages and custom messages.Supports viewing delivery rate, display rate, and click-through rate at the message ID level.Supports viewing valid target count, send count, display count, and click count at the message ID level. |
| Message Loss Analytics |
Supports viewing message loss analytics at the message ID level by platform and channel, with support for two-level statistical analysis of loss reasons.Supports loss count analytics across a total of five stages: {Planned Target}-{Valid Target}-{Send Count}-{Delivery Count}-{Click Count}. |
REST API Capability Support
| API Item |
Feature Description |
| PUSH API |
Through the PUSH API, developers can complete all WebPush message push functions and easily build push operation plans in their own backend systems.The API provides more powerful and flexible functional interfaces than the push portal page. |
| Report API |
Provides various analytics data query functions, making it convenient for developers to promptly understand message status and user data.The API provides functional interfaces for obtaining push message analytics data and user analytics data. |
| Schedule API |
Through the Schedule API, developers can implement scheduled push delivery for all messages. |
| Tag Alias API (Device API) |
The Device API is used to query, set, update, and delete device tag and alias information on the server side. |
