APP Push from EngageLab is a professional app messaging push service platform with an average daily message volume exceeding 10 billion. AppPush supports Android, iOS, HarmonyOS, and other platforms, offering easy and fast SDK integration, high-speed and stable push channels, powerful, flexible, and easy-to-use open API interfaces, and web-based operational features such as notification creation, performance analysis, and troubleshooting.
Supported Channel Types
| Push Channel |
FCM |
HUAWEI |
Honor |
XIAOMI |
MEIZU |
OPPO |
VIVO |
APNs |
HarmonyOS |
| Support Status |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported Message Types
| Message Type |
Notification Message |
Custom Message |
| Support Status |
Supported |
Supported |
Supported Notification Styles
| Notification Style |
Default Style |
Thumbnail Style |
Large Image Style |
Text Style |
Inbox Style |
Custom Style |
| Support Status |
Supported |
Supported |
Supported |
Supported |
Supported |
Supported |
For style details, see Local Notifications.
Supported Sending Strategies
On the API side, developers can define sending strategies with vendor channels as the unit of granularity.
| Message Type |
Sending Strategy Field |
Sending Strategy Field Values and Definitions |
| Notification message sending strategy |
distribution_new |
mtpush: indicates that push messages are forcibly delivered through the EngageLab channel.fcm_mtpush: indicates that push messages are forcibly prioritized through the FCM channel, and if invalid, then through the EngageLab channel.pns_mtpush: indicates that push messages are forcibly delivered through Xiaomi / Huawei / Meizu / OPPO / VIVO channels, and if invalid, then through the EngageLab channel.mtpush_fcm: indicates that for users with the FCM + domestic vendor combination type, push messages are prioritized through EngageLab, and if EngageLab is offline, then through the FCM channel, with FCM serving as an auxiliary channel.mtpush_pns: indicates that for users with the FCM + domestic vendor combination type, push messages are prioritized through EngageLab, and if EngageLab is offline, then through the vendor channel, with the vendor channel serving as an auxiliary channel. |
Supported Statistical Analysis
App-Dimension Statistics Features
| Statistics Feature |
Description |
| Data Overview |
Supports real-time statistics for message data 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 enablement rate data.Supports viewing historical push conversion trend data by platform and by channel.Supports viewing historical push message loss statistics by platform, by channel, and by stage. |
| Message Push Statistics |
Supports viewing historical push data by platform, by channel, by message type, and by app version.Supports viewing metrics 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 Statistics |
Supports viewing historical push user data by platform, by channel, and by app version.Supports viewing metrics such as new push users, online users, active users, and uninstalled users within a custom time range by day or month. |
MessageID-Dimension Statistics Features
| Statistics Feature |
Description |
| Message Push Statistics |
Supports push conversion statistical reports for four basic message types: notification messages, custom messages, SMS, and in-app reminder messages.Supports viewing delivery rate, display rate, and click-through rate at the msgid dimension.Supports viewing valid target count, send count, display count, and click count at the msgid dimension by platform and by channel. |
| Message Loss Statistics |
Supports viewing message loss statistics at the msgid dimension by platform and by channel, with two-level loss reason analysis.Supports loss count statistics across a total of 4 stages: {planned target} - {valid target} - {send count} - {delivery count} - {click count}. |
Supported REST API Capabilities
| API Item |
Description |
| PUSH API |
Through the PUSH API, developers can complete all AppPush message push functions and easily build push operation plans in their own operational backend.The API provides more powerful and flexible functional interfaces than the push portal page. |
| Report API |
Provides various statistical data query functions, allowing developers to promptly understand message status and user data.The API provides functional interfaces for obtaining push message statistics and user data statistics. |
| Schedule API |
Through the Schedule API, developers can implement scheduled push for all messages. |
| Tag Alias API (Device API) |
Device API is used on the server side to query, set, update, and delete device tag and alias information. |
Push Test Mode
AppPush test mode provides developers with an independent test environment outside the production environment, helping verify push configuration and effectiveness to ensure a high-quality release.
Environment Switching and AppKey Management
- AppKey and master secret distinction:
The production environment and test environment use different AppKey and master secret values. When switching to test mode, the system automatically generates a test AppKey and copies the relevant configuration from the production AppKey. The backend binds and associates the two to determine VIP status and synchronize information.
- Default environment: After entering the Portal, the production environment is displayed by default, and developers can manually switch to test mode.
- Reset support: The test AppKey supports an independent master secret reset.
Synchronization and Independent Management in Test Mode
- Synchronized information: When creating a test application, the system copies the following content from the production application:
- Application name and icon
- Application information synchronization: Information such as the application name and icon of the test application is synchronized with the production application in real time.
- VIP status synchronization: Information such as the VIP status and service period of the test application is synchronized with the production application in real time.
- Independent configuration: The test application supports separate configuration of callbacks, security settings, and integration settings.
Usage Limits in Test Mode
- QPS limit: 10
- Number of SDK-registered users: Up to 1,000. Once the limit is exceeded, no new users can be registered. It is strongly recommended that you record the registrationID and clean up regularly. Delete User API.
- Tag and alias binding limits:
- Tags: Up to 50 can be bound
- Devices bound per tag: Up to 10
- Tags bound per device: Up to 10
- Validity dependency: The availability of the test AppKey is bound to the production AppKey. When the production AppKey becomes invalid, the test AppKey also becomes unavailable.
- Service limitation: The test AppKey does not support purchasing VIP services, and its benefits fully follow the corresponding production AppKey.
This push test mode provides developers with a flexible and independent environment to efficiently verify push configurations before official launch, ensuring better control over push effectiveness and user experience.
